Adding custom fields

Still need help?

The Atlassian Community is here for you.

Ask the community

You can create a custom field to collect information that isn’t available in the default system fields. Before you start, read our tips on creating custom fields, so your Jira instance isn’t cluttered with too many fields.

Custom fields are always optional fields. This means that you can create a new custom field without making changes to existing issues. The existing issues will contain no value for the new custom field, even if a default value is defined for it.

After you make changes to custom fields, you should reindex your Jira.

For all of the following procedures, you must be logged in as a user with the Jira administrators global permission.

Tips for creating custom fields

Here are some tips on creating and managing custom fields:

Limit the number of custom fields

Pay attention to how many custom fields you define in Jira. A thousand or more is a large number and may affect Jira's performance. Check out more about the issue in

Combine field content

If you just want to make sure that a user remembers to enter some information into the field, consider a multi-line custom text field with a text template as a default value. The Atlassian Marketplace has apps that provide such functionality.

Avoid duplicating fields’ names

You shouldn’t create new custom fields with the same names as the existing custom fields. Always check to see whether a custom field with the same name already exists before you create it. 

If you create custom fields with the same names, it’ll be confusing for users to choose the correct field in JQL searches. 

Also, don't create custom fields with the same name as the default Jira fields. For example, having two "Status" fields (a default and a custom one) will cause inconveniences in search or issue management. 

Make names as generic as possible

Give custom fields non-specific names that can be reused in other places later. For example, instead of naming a field "Marketing Objective", name the field "Objective", and write a description in the field configuration that lists the Jira projects where the field is used.

On this page:

Custom field types

When creating a new custom field, you should first set a type of this field. The type indicates how your custom field will display and function, as well as what values it can accept.

The following table lists a wide array of custom field types that Jira provides to cover various use cases of what information must be present in issues and how.

By default, you’re offered to select from standard field types when adding a new custom field. To open the full list of the custom field types, select All in the dialog window.

Custom field typeDescription

JIRA CORE custom field types

Checkboxes STANDARD

Allows selecting multiple values from the list.

Checkboxes is one of the custom field types for which you should create options. Tell me how

Date picker STANDARD

Allows selecting a date

Date time picker STANDARD

Allows selecting a date and time


Allows adding labels to issues to facilitate issue categorization and search

Number field STANDARD

Stores and validates a floating point number

Radio buttons STANDARD

Allows selecting on value from the list.

Radio buttons is one of the custom field types for which you should create options. Tell me how

Select list (cascading) STANDARD

Allows selecting values based on their parent-child relation.

Select list (cascading) is one of the custom field types for which you should create options. Tell me how

Select list (multiple choices) STANDARD

Allows selecting multiple values from the list.

Select list (multiple choices) is one of the custom field types for which you should create options. Tell me how

Select list (single choice) STANDARD

Allows selecting one value from the list

Text field (multi-line) STANDARD

Creates an unlimited text area where a user can enter a long text with many lines

Text field (single line) STANDARD

Creates a text box where a user can enter a one-line text, no longer than 255 characters including spaces


Allows entering one URL

User picker (single user) STANDARD

Allows selecting one user

Group picker (multiple groups) ADVANCED

Allows selecting multiple user groups

Group picker (single group) ADVANCED 

Allows selecting one user group

Project picker (single project) ADVANCED

Allows selecting one project that the user can view in Jira

Text field (read only) ADVANCED

Creates a read-only text label for setting values programmatically. A value can contain no more than 255 characters, including spaces.

User picker (multiple users) ADVANCED

Allows selecting multiple users

Version picker (multiple versions) ADVANCED

Allows selecting multiple versions

Version picker (single version) ADVANCED

Allows selecting one version

JIRA SOFTWARE ONLY custom field types

Global rank ADVANCED

Jira Software automatically creates the Rank custom field of this type. The Rank field allows you to assess the importance or urgency of your issues and prioritize them, move them across sprints, or group sub-tasks under particular parent issues. Learn more about ranking

Hidden job switch ADVANCED

Sets a hidden switch programmatically to choose whether or not to create a Perforce job.

Jira released version history ADVANCED

Allows setting a custom release version

Job checkbox ADVANCED

Creates a checkbox to choose whether or not to create a Perforce job.

Original story points ADVANCED

Stores the original number of story points assigned to an issue before the work on it is started

Creating a new custom field

To create a custom field:

  1. In the upper-right corner of the screen, select Administration  > Issues.

  2. Under Fields (the left-side panel), select Custom fields.

  3. Select Add custom field.

  4. In the Select a field type modal dialog, select All to make sure you can see all available field types.

  5. Select the field type and select Next. For example, let’s select the Checkboxes field type.

  6. Configure the field by entering its name, description, and options if required. Select Next.

    You’ll see the Name as the custom field's title when entering and retrieving information on issues. You’ll see the Description beneath the field when creating new issues and editing existing issues, but not when browsing issues.

  7. Configure the context for the field.

    What are contexts?

    Custom field contexts are different configurations of the same field. By configuring multiple contexts, you can use different default values and options for different projects or make the field applicable only to chosen issue types or projects. It’s generally a performance-wise idea to limit the application of a custom field to the projects that will actually use it. You can configure the context later.

    Learn how to do it in Configuring custom field contexts.

  8. Select projects where the custom field must be applied.

  9. Select Create.

Now, you can associate the new custom field with issue screens and then add the field to your issues. Learn more

Associating a custom field with an issue screen

After you create a custom field, you’ll be brought to the Screens page. Learn more about screens

Here, you can choose on which issue screens your custom fields should be displayed. For example, on the Default screen or Resolve issue screen.

To associate the field with the screens, select the checkboxes next to the desired screens and select Update

The custom field will be available on all issue screens for which you’ve enabled it. If you don’t select any screen here, you won’t see the custom field when creating or editing an issue.

Editing existing associations

You can always edit the associations between the custom field and selected screens. To do this:

  1. In the upper-right corner of the screen, select Administration  > Issues.

  2. Under Fields (the left-side panel), select Field configurations.

  3. Select the field configuration.

  4. Find your custom field in the list and select Screens.

  5. Change the associations and select Update.

You can also add custom fields into existing issues regardless of the associations with screens.

Adding a custom field directly to an issue

Even if your custom field isn’t associated with an issue screen, you can still add this field to existing issues of a particular type. Before doing this, ensure you’ve enabled the field for the desired issue type

To add a field to an issue:

  1. Open an issue.

  2. Select Admin > Add field. In the dropdown, select the field you want to see in the issue view.

  3. Select Edit field to set a value for the field immediately.
  4. Select Submit.

For all of the following procedures, you must be logged in as a user with the Jira administrators global permission.

You’ll see the custom field either in the Details block or in the Edit issue screen. If the field isn’t editable, learn how to change that.

The association with the corresponding issue screens will be generated automatically.

The field will become available in all issues of all types for which you’ve enabled it. For example, your field is enabled only for bugs. So, as soon as you add it to one bug, the field will appear in all bugs either of specific projects or across your instance, depending on the context you’ve configured for the field. 

Enabling the field in the board or backlog view

You can add the field from the Jira administration menu. See Configuring a screen's tabs and fields for instructions.

Alternatively, you can do this directly from the issue. As an example, let’s enable the “Issue labels” custom field that we added in the previous section:

  1. Go to the board or backlog view and edit any existing issue.

  2. In the upper-right corner, select Configure fields > Where is my field? to open the field helper.

  3. Enter the name of your custom field. In this case, “Issue label”.

  4. You’ll see the field’s status and details on why your field isn’t displayed and how to update the field’s configuration.

  5. Update the field’s configuration for the Project and issue type scope from the Issue label configuration page. Check out Configuring custom field contexts for details.

  6. Update Field Screen configuration from the OP: Scrum Bug Screen Screen configuration page. See Making the added field editable in the issue view section from Configuring the issue view for details.

Changing issue types where custom fields are added

You can always change the issue types for which you’ve added custom fields. For example, the field can be added only to bugs, but you want to add it to issues of all types.

To change issue types:

  1. In the upper-right corner of the screen, select Administration  > Issues.

  2. Under Fields (the left-side panel), select Custom fields.

  3. Find the field in the list and select Configure in Actions.

  4. On the page with configurations, select Edit configuration.

  5. Go to Choose applicable issue types and select Any issue type

Learn more about how to edit custom fields

You can add the field to issues of all types. The association with the corresponding issue screens will be generated automatically.

Next steps

If you want to change the field’s context, see Configuring a custom field

You can also find more custom fields from apps on the Atlassian Marketplace (for example, the Jira Toolkit). 

To build your own custom field types, see this tutorial from the Jira Developer Documentation.

tip/resting Created with Sketch.

To discover more opportunities of using custom fields in Jira, try one of the apps from the Atlassian Marketplace:  

Reindexing Jira

Changes to custom fields affect Jira search index. After you make changes to any settings, you'll get the following message in the Administration view:

We recommend that you perform a re-index, as configuration changes were made to 'SECTION' by USER at TIME. If you have other changes to make, complete them first so that you don't perform multiple re-indexes

The message means that configuration changes have been made to Jira but haven't yet been reflected in the search index. Until Jira search index has been rebuilt, some search queries from Jira might return incorrect results. 

To avoid any discrepancies, you should rebuild Jira search index.

If you want to know after what actions with custom fields you need to re-index Jira, check Reindexing in Jira after configuring an instance for tips.

Learn more about other major configuration changes when Jira reindex is required

Last modified on Apr 24, 2023

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.