Configure field layout in the issue view

Still need help?

The Atlassian Community is here for you.

Ask the community

This page is about configuring the fields that appear in the new Jira issue view for classic projects. If you're working in a next-gen project, take a look at Customize an issue's fields in next-gen projects.

For information on configuring the old issue view, go to Defining a screen.

Choosing which fields appear on your team's issues, and which of those are most important, can help your team get more done in less time. If there are a few fields you fill out for every bug, for example, it makes sense that those fields are always visible and probably somewhere towards the top of the issue view. If you're a project administrator, you can set up the issue view in the way that works best for your team.

When choosing which fields to show and their position on the issue, you can also sort those fields into two categories—primary and secondary fields—to determine how they appear and behave in different views.

The available fields for an issue type are the ones added in the global screen configuration for viewing that issue type. To add more existing fields issue types, you need to visit that screen and add them. If you're a Jira admin, there'll be a link to the global screen configuration from the Issue layout page.

To add brand new fields, see Adding, editing, and deleting a custom field.

Configure field layout for issue types

When configuring issue layout, you're configuring it for one or more issue types in a project. For example, when you configure the issue layout for bugs in a project, all bugs in that project will share that configuration.

  1. From your project's sidebar, select Project settings > Issue layout.
  2. Select Edit layout for the issue type or types you'd like to configure.
  3. Add, remove, and drag fields in the field categories until you're happy with the setup.
  4. Choose Save changes.

If a group of issue types—tasks and subtasks, for example—use the same view issue screen, which they do by default, you'll configure the fields for those issue types all together as a set.

Field categories

Primary fields (always show)

Primary fields are those fields that are important to most, if not all, issues of a particular type (stories or bugs, for example). They're always visible when you open the issue, and they might be fields you and your team update on a regular basis. They'll likely also be visible in other places in Jira, like when you're viewing an issue as a card on a board or in a queue.

Examples of primary fields could be things like assigneecomponent, and due date, but they can be any field you consider important enough to show on every issue of that type. You may also choose to make primary fields, required fields.

When you open an issue, primary fields are always shown in the issue's context area above the Show more link.

Secondary fields (hide under "show more" when empty)

Secondary fields are those that you'd fill in sometimes, to add a little extra context to the issue. When they're empty, they appear under the Show more link in the issue's context area; when you add a value to a secondary field, it moves to the bottom of the context area just above the Show more link.

Hidden fields

Fields can be available to use for an issue type, but not actually shown in the issue view. When configuring the layout for an issue type, drag fields to the right side of the screen and drop them in the Hidden fields section.

  1. Issue fields: Primary fields appear at the top of this section, above the Show more link.
  2. Show more: Secondary fields are hidden behind this link when they're empty. When they have a value, they'll appear above Show more.

Last modified on Feb 6, 2019

Was this helpful?

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