(Editing this question as I incorrectly entered it previously) We have created a custom field called "Acceptance Criteria". In all the screens definitions, this new fields is ordered after the Description field but in the following screens/view, Acceptance Criteria always appears before Description: * Summary view in the Board * Detailed View of the Issue The following forms respect the defined order: * Create a new issue * Edit issue I can see that the custom field appears in a section called Details while Description has a section of its own. How can I make Description the first field displayed in all these views ?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Ordering custom field

Johann Moro

(Editing this question as I incorrectly entered it previously)

We have created a custom field called "Acceptance Criteria". In all the screens definitions, this new fields is ordered after the Description field but in the following screens/view, Acceptance Criteria always appears before Description:

Summary view in the Board
Detailed View of the Issue

The following forms respect the defined order:

Create a new issue
Edit issue

I can see that the custom field appears in a section called Details while Description has a section of its own. How can I make Description the first field displayed in all these views ?

Accepted answers

Nic Brough -Adaptavist-

Yes, you can have them in JIRA.

All comments

Nic Brough -Adaptavist-

Yes, you can have them in JIRA.

Johann Moro

I have edited my question as I clearly submitted a question when I intended to do a search.

Nic Brough -Adaptavist-

Answers seems to encourage that, I just respond to prompt people to do exactly what you've just done!

The JIRA view screen rearranges a number of fields, gathering together the people, date and "system" fields (including description) into distinct sections, which is why it's ending up in a funny place. I'm afraid this is deliberate and you can't do anything about it without hacking the core code that displays that screen.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-core