I don't know how we mess the system but since 2 days each time we are creating a ticket/issue, the system refusing it and add to the screen the field "resolution" to force us to define a resolution status.
We don't want to "resolve" the issue at the creation.
This happens for all our projects whatever workflow/screen.
How to go back to the standard setup?
The resolution field is not technically mandatory, but it does not have an "empty" value to select, so it always gets set if it is placed on a create or edit screen.
You must not put the resolution field on any create or edit field - only view or transitions into "end" type status.
>The field is always mandatory
I'm afraid that is incorrect. The resolution field is NOT mandatory in JIRA terms. It is optional. It must be optional, because the users need to leave it empty until such a time as an issue is resolved. The definition of a mandatory field is "it must have data in it".
So, the field is optional
If you put it on a screen that allows updating an issue though, then your users will fill it in because it always has a default setting, and no option to let them leave it blank. Which is why you never put it on the create or edit screens, only transition screens to "end" status.
As Nic said, ANY time the field is presented on an edit screen it must be populated. It should ONLY be put on the transition screen used to set it. It will automatically appear in the issue details so there is no need to put it on any other screen than the transition ones.
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