Customize an issue's fields in next-gen projects

robotsnoindex
description

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

Are you on the right help page?

The following information only applies to team-managed projects.

To check which type project you need help with, look at the bottom of your project’s left-hand sidebar:

Specific types of work require specific kinds of information for your team to successfully complete their tasks. Jira can collect and display this information to provide your team the context they need to get the job done.

This extra, customizable information appears in an issue's fields. You can customize each issue type to show different fields and collect the exact information your team needs to succeed.


You must have the administrator role in your project to do the things described on this page. Learn more about team-managed 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 Description fields in your project's settings appear in the main content area of your issues.
  2. Fields you add to Context fields in your project's settings appear on the right side of your issues.
  3. If you drag fields under the Hide fields below dotted line, they appear on your issues when someone completes the field. If the field is empty, it’s hidden. Select Show x more fields when viewing an issue to interact with hidden 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. Jira highlights the areas you can drop the field into.

In Jira Work Management, you also have the option below:

  1. From your project's list view, select the plus icon at the top right or when hovering each column.

  2. Select the the field you want to add from the dropdown list.

The fields list contains:

  • fields you created on other issue types
  • fields Jira Software created for you
  • fields 3rd-party apps created for you
  • global fields that exist across your site

The list show all fields not yet associated with any issues. Using the same field between more than one issue type makes it easier to sort, search, and report on those fields.

When a field appears on more than one issue in the same project, the fields share the same name and description. If you change the name in one issue type, it will change in the others that use that field. Checkbox and dropdown fields also share their available options. But, the field can have a unique default value on each issue type.

Fields in team-managed projects are contained within the project itself. Currently, you can't share a field created in one team-managed project with another team-managed project, or with company-managed project. Similarly, you can't use a custom field created in a company-managed project on your team-managed project issues.

You can rearrange the order of the fields in your project settings.

To remove a field from your list view, select Hide field in the dropdown at the top of the column. Select Edit > Delete to delete it.

Default fields

By default, Jira Software adds the following fields to your issue types:

  • Summary – a brief, one-line summary of the task. This field is always required in Jira.

  • Description – details of the work needed to complete the task.

  • Status – the current workflow status and available transitions that move the issue through the workflow.
  • Assignee – the person assigned to the task.
  • Labels – tags used to group, filter, or search for issues.
  • 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.

Default fields in Jira Work Management:

  • Summary – a brief, one-line summary of the task. This field is always required in Jira.

  • Description – details of the work needed to complete the task.

  • Status – the current workflow status and available transitions that move the issue through the workflow.

  • Assignee – the person assigned to the task.

  • Labels – tags used to group, filter, or search for issues.

  • 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.

  • Due date – the agreed time and date when the issue or task should be resolved.

  • Start date – the date when work began on a task, issue, or epic.

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. Only Jira administrators can customize what priority levels are available across their Jira site. Learn more about configuring priorities.
  • Environment – the specific technical environment that relates to the task. For example, "Chrome 78.0.3904.97, macOS Version 10.14.6, javascript V8 7.8.279.23".
  • Time tracking – an interactive field that allows people to log work hours and estimated time remaining on a task. Learn more about logging time on issues.

If you've enabled project features, like sprints or estimation, you might see a few other fields:

  • Sprint – labels the issue or task with the sprint it belongs to. This is useful in filtering, sorting, and reporting. The Sprint field is created automatically when you enable the Sprints feature. Learn more about the sprints feature.
  • Story point estimate – the estimated amount of effort that the issue or task should take, expressed as a numeral (not necessarily equivalent to an amount of time). The Story points field is created automatically when you enable the Estimation feature, and select Story points as your estimation statistic.
     Learn more about estimation.
  • Original estimate – the estimated amount of effort that an issue or task should take equivalent to an amount of time. The Original estimate field is always available. The Original estimate field is created automatically when you enable the Estimation feature and select Time as your estimation statistic. Learn more about estimation.


Required fields

Use required fields to mark an issue type’s most important details.

  1. From your project's sidebar, select Project settings > Issue types.

  2. Select the issue type you want to edit.

  3. Select the Required checkbox for any fields you want to make mandatory.

  4. Select Save changes.

Once saved, new issues of that type can’t be created unless the required field is filled out.


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 a field, drag the type of field you want to create. Jira highlights the areas you can drop the field into. Learn more about the available types of custom fields.
  4. Give your new field a name (up to 120 characters).
  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 your project's other issue types in their Previously-created fields lists.

You can create up to 50 custom fields in your project.

You can only add a custom short text field to the Context section of your issue types. Similarly, you can only add a custom paragraph field to the Description section of your issue types.

In Jira Work Management you also have the following option:

  1. Go to List view to view all issues

  2. Hover over each column to see the plus icon or select the plus icon at the top right.

  3. Select Create a new field.

  4. In the drop down menu, select the type of field you want to create then give it a name.

  5. When you have entered the field name, select Create.

  6. A new sidebar will appear where you can add more details for your field.

    The name you select appears as the custom field's title wherever the field appears. The description appears below the field when creating and editing issues, but not when browsing issues.

Edit custom fields

To edit a custom field:

  1. From your project's sidebar, select Project settings > Issue types.
  2. Select the issue type whose field you want to edit.
  3. Locate the field and click its card in the list.
  4. Edit any of the field's options, like its default description, default values, or other options.
  5. Select Save changes.

Your changes update across all your issue types that use the field in your project.

In Jira Work Management you can also choose the edit option in the dropdown at the top of the column in list view.


Reuse custom fields

You can reuse fields from company-managed projects in your team-managed project

You can only reuse fields with global contexts. Learn more about global contexts.

To reuse custom fields:

  1. From your project's sidebar, select Project settings > Issue types.

  2. Select the issue type you want to add custom fields.

  3. Search for fields using the search bar on the right under Fields. Alternatively, select a field from Suggested fields, which contains a list of all issues that were recently created, or are used in other issue types of the project.

  4. Drag and drop fields to move them to a section on the left.

  5. Select Save changes.

tip/resting Created with Sketch.

Some fields have icons next to them to represent the project they were created for, and can be used in other issue types of the same project. You can customize these fields for your team’s needs.

Some fields in company-managed projects may have configurations and contexts that make these fields unavailable in the issue view, even if you drag the field to one of the sections in the issue layout. As a result, these fields will not show up on the issue view.



Last modified on Dec 12, 2023

Was this helpful?

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