JIRA 4.0 : Changing scope of existing custom fields
This page last changed on Jun 14, 2009 by rosie@atlassian.com.
OverviewIn JIRA, custom fields can apply to all issue, all issues of a certain type, or issues in a single project. Occasionally one wants to change the scope of a custom field, eg. to make a project-specific custom field global. JIRA does not yet have a means of doing this in the interface, but it is easy to do by manipulating the database directly. Here we show how to do it. Load a SQL console.Load your JIRA database in a SQL console. This operation is database-dependent. Oracle users will run sqlplus, MySQL users mysql or mysqlcc. Users of JIRA Standalone should follow this guide. Display the customfield table.By running the query select * from customfield; you will see how custom fields are defined in the database: Here, we have one global and one project-specific custom field. Edit the table flags.Say we wanted to make the project-specific custom field global. We should set the custom field's project field to null: Restart JIRAExit the SQL console and restart JIRA. The scope of the custom field should have changed. |
![]() |
Document generated by Confluence on Oct 06, 2009 00:26 |