rearranging fields in a screen is not working fully?

Question

the product people at my company asked for a specific custom field (acceptance criteria) to be under the "description" field in the story item.

i went to the screen on the specific scheme used for the project and changed it.

when creating or editing a story item i can see the field "acceptance criteria" in the correct place but when you view the issue the field is up and not in the place i configured.

anyone knows why it's like that?

it's important that when viewing a story item i will see the description first and then the acceptance criteria.

Jack Hunter _HeroCoders_ · Answer

Hello @Eli Moshe,

As Nic explained you cannot control where the field is located precisely.

If Jira custom field or its location does not work as expected then you might consider third-party add-on.

My team created Issue Checklist app that solves the acceptance criteria and the definition of done problems through a list of check items. We also use it for testing notes and as a simple ToDo list so the number of possible use cases is very extensive.

It is located on Jira issue page below Description as shown in the screenshot:

Issue Checklist allows blocking resolving the case if not all items/criteria are completed. It also allows to mention users, link issues, display checklist progress in various places (including issue cards on Agile boards), define a default checklist for a project or issue type and more.

I hope that helps.

Cheers,
Jack

Nic Brough -Adaptavist- · Answer

The issue view takes the list of your fields and re-arranges them into a set of panels.  Dates and times get pulled out into a date panel, people and groups go into a panel, the system fields go into another, estimate and work-log another.  Description, links and subtasks all get their own panels.

Once it's pulled those out, the rest of your fields are placed in the custom fields panel.  That will include your "acceptance criteria".  But, of course Description and others have been pulled out elsewhere.