Documentation for JIRA 4.0. Documentation for other versions of JIRA is available too.

This is all obsolete as of JIRA 3.2, where one can change the scoping of custom fields from within the field interface

Overview

In 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 JIRA

Exit the SQL console and restart JIRA. The scope of the custom field should have changed.

  • No labels



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.