robotsnoindex

description

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.

description

Define and customize the fields that appear in request type forms and internal views. Add more fields or edit the view for each of your next-gen request types.

Are you on the right help page?

The following information only applies to next-gen projects.

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

  • If you see an icon stating You’re in a next-gen project with Give feedback and Learn more menu items, you're in a project.

  • If you don't, you're in a classic project. Check out our classic project documentation.

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.

Specific types of requests require specific kinds of information for your team to successfully complete their tasks. Jira Service Management 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 a request's fields. You can customize each request 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 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 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.

How fields appear in your customer portal and to your agents

When you add fields to your request types, they appear on that type’s request form in your customer portal. You can also add fields for your agent’s eyes only.

  1. Fields you add to the Portal fields list in your service project's settings appear in the customer portal. You can give these fields a customer-facing display name to make it easier for customers to submit the right information in their requests.

  2. Fields you add to the Internal fields list in your service project's settings appear in the agent’s view of customer requests. These always show if someone's completed the field. But they may be hidden if the field is empty (see #3).

  3. The first six fields in your Internal fields list will always show. Jira Service Management hides any additional fields in that list if they're empty. An agent can select Show more when viewing a request 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.

The previously-created fields list contains:

  • fields you created on other issue types
  • fields Jira Software created for you
  • fields 3rd-party apps created for you

You can drag previously-created fields into your issue type to reuse them. 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 type, 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 next-gen projects are contained within the project itself. Currently, you can't share a field created in one next-gen project with another next-gen project, or with a classic project. Similarly, you can't use a custom field created in a classic project on your next-gen project issues.

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

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

Add, reorder, or remove fields

To add a field to your request type:

  1. From your project's sidebar, select Service project settings > Request types.

  2. Select the request 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.

The previously-created fields list contains:

  • fields you created on other request types
  • fields Jira Service Management created for you
  • fields 3rd-party apps created for you

You can drag previously-created fields into your request type to reuse them. Using the same field between more than one request type makes it easier to sort, search, and report on those fields.

When a field appears on more than one request type, the fields share the same name and description. If you change the name in one request 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 and display name on each request type.

Fields in next-gen service projects are contained within the project itself. Currently, you can't share a field created in one next-gen service project with another next-gen service project, or with a classic project. Similarly, you can't use a custom field created in a classic project on your next-gen service project's requests.

To rearrange the order of fields, drag and drop the fields into the order you prefer.

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

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.

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.
  • Due date – the agreed time and date when the issue or task should be resolved.
  • 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.
  • Start date – the date when work began on a task, issue, or epic.

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 point estimate field is created automatically when you enable the Estimation feature. Learn more about estimation.

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

Create custom fields

To create a new custom field:

  1. From your project's sidebar, select Service project settings > Request types.

  2. Select the request type you want to edit.

  3. Under Create new 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, setting a default value.

  6. Add a display name for the field. The display name is the customer-facing label in the request form on your portal.

  7. Select Save changes.

Your new field is also available to your service project's other request types in their Previously-created fields lists.

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

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.

Edit custom fields

To edit a custom field:

  1. From your project's sidebar, select Service project settings > Request types.
  2. Select the request 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 request types that use the field in your service project.

Make a field required

Required fields force people to complete the field when creating or editing a request. Usually, these fields contain the most important information needed to work on the request.

You can only require fields that appear above the Hide fields below line.

To make a field required:

  1. From your project's sidebar, select Service project settings > Request types.

  2. Select the request type you want to edit.

  3. Select the field you want to make required in your list of fields.

  4. Click the field to expand its options and tick the Required checkbox.

Take care when making a field required. Any request types that share this field also share the required option.

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.