Customize an issue's fields in next-gen projects


Define and customize the fields that appear in your next-gen software issues' details. Add more fields or edit the view for each of your issue types.

The foundation of every Jira issue is its key, summary, and a status. With this information, you can track simple tasks and stay on top of your project's work.

We know that some tasks require more information to help along the team taking on that work. So, Jira can collect and display more information to provide context and get work on its way to done.

This extra, customizable information appears in an issue's fields. And, you can customize each issue type to show different fields.

You must have the administrator role in your project to do the things described on this page. Learn more about next-gen project roles.

How fields appear on your issues

When you add fields to your issue types, they appear on all issues of that type.

  1. Fields you add to PRIMARY FIELDS in your project's settings appear on the right side of your issues.
  2. Fields you add to SECONDARY FIELDS in your project's settings also appear on your issues. But, if the field is empty, it's hidden. Select Show more when viewing an issue to interact with these fields.

Add, reorder, or remove fields

To add a field to your issue type:

  1. From your project's sidebar, select Project settings > Issue types.
  2. Select the issue type you want to edit.
  3. Drag fields from the toolbar into the list of fields.

To remove a field, drag the field back into the fields toolbar.

To rearrange the order of fields in the new issue view, drag and drop the fields into the order you prefer.

Fields are arranged by global rank in the old issue view. If you need to rearrange fields in this view, ask your Jira admin for help.

Default fields

By default, Jira adds a few fields to your issue types that we think help provide context to your project's work. They are:

  • Assignee – the person assigned to the task.
  • Reporter   the person who brought up the issue or task. Usually, this is the same as the person who created the issue. Some teams create issues in a working group or using a shared computer. These teams might need to adjust the reporter when creating issues.
  • Labels – tags used to group, filter, or search for issues. 

Jira also comes with a few commonly-used fields you might consider adding:

  • Priority – the importance of the issue or task in relation to others in the project.
  • Due date – the agreed time and date when the issue or task should be resolved.
  • Time tracking – the estimated and remaining time left to complete the task. Read more about logging time on issues.

We mark these fields by Jira in the fields toolbar. Some can't be edited. But, you can easily remove them from your issue types.

Create custom fields

To create a new custom field:

  1. From your project's sidebar, select Project settings > Issue types.
  2. Select the issue type you want to edit.
  3. Under Create new field, drag the type of field you want to create. Learn more about the available types of custom fields.
  4. Give your new field a name.
  5. Configure any extra field options, like adding a description for your team or setting a default value.
  6. Select Save changes.

Your new field is also available to other issue types in your project.

For technical reasons, you can’t make the Assignee or Reporter fields provided by Jira required. Let’s just say if you did make them required, it wouldn’t make that much of a difference anyway.

A note about field names, descriptions, and certain options

If you edit a field that appears on more than one issue type, you might notice a warning that some changes apply to other issue types that use the field. To help with searching, sorting, and reporting, fields retain their name and description across all issue types in your project. Checkbox and dropdown fields also retain their available options across all issue types in your project.

Everything else can vary between issue types, including a field’s default value, whether it’s required, and where it appears in an issue type’s list of fields.

Last modified on Jun 20, 2019

Was this helpful?

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