Currently, the "Acceptance Criteria" field is listed above the "Description" field. All the users are taken back and feel uncomfortable to see the acceptance criteria before the description field.
You would need to download the source code of Jira, find the modules that render the issue view, amend them so that they understand they need to move your field, recompile (at least that module) and redeploy
You'll be unsupported, and have to repeat this on every upgrade. I cannot recommend doing it.
Are there any plans to change this? It is a big inconvenience to have the acceptance criteria above the description. Is there any reason why set fields are in set orders? We are in the process of implementing SCRUM. We have been using Jira for some years, but now we need t tailor the story view to encourage the team to enter the correct data for each story. Things like this make that a harder task.
@Kai Forsyth, is using 6.4.5, maybe it's using the classic issue detail view.
@Balaji Madana, are you refering to the standard view issue screen when you access the issue?
To order those fields you need to edit the screen designated as the view screen for that issue type on that project.
This can be done from the project administation, selecting the issue type screen scheme and then follow the link to the screen scheme and finally the view issue screen:
Once you enter the screen configuration you can drag and drop the fields to reorder
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs