I have added a validator to the 'Resolve Issue' transition in my workflows to make some fields, including 'Resolution' mandatory.
When an issue in the 'Open' state is edited JIRA is making 'Resolution' mandatory.
Most odd, help!
I suspect you are mixing up "mandatory" with "there is no option for none when you put the resolution on a create or update screen".
You must only place the resolution field on transition screens that take an issue into a status you want to think of as "closed".
You do NOT need to place any validation on "resolution" - if it's on screen, it gets set. TO avoid setting it, make sure it is not on Edit or transition screens where you don't want to set it.
I was unaware that resolution was mandatory by default.
I'll update my workflows to remove the typo
With regards having it on the view/edit screen (and adding a 'None' option) or not; I'll need to check with my users on their preference.
Ah, um, it's not "mandatory" at all. It does not have a "none" option. So your users fill it in by accident if you put it on a screen. JIRA's concept of "mandatory" applies from issue create onward. If you want to add a "none"option to it, that actually means coding - it's not a configuration or easy tweak - the field is coded with no "none" option!
ARGH! NO! *Remove* it now. Immediately. Kill it with fire. JIRA considers *any* value in there to mean "resolved". If you select your new "none" option on an issue, then that issue is RESOLVED, Done, ended, deaded, killed, closed, whatever you want to call it.
The values you have in that list are *just* labels for different numbers in the background. JIRA doesn't care what they are (the values are for humans), the functionality says "is there a resolution?" If there is, even if it's "none" or "unresolved", then there IS a resolution.
I had the same issue, solved it by creating a separate 'Create' screen which does not show Resolution. While testing this screen I came across a bug:
Cannot switch between projects that use different schemes. When Configure fields is used, toggling between All and Custom Fields results in an error.
I still consider this a workaround; resolution should only be mandatory for issues in status Resolved or Closed. The strikethrough, IMHO should depend on the status and not on whether or not a resolution in present.
I'd take a similar approach and bin "resolution" as the "is resolved" flag completely. I'd favour a set of meta-status (similar to the to-do, in progress, done categorisation in Agile) that answer the question, and demote the resolution field to nothing more than a flag.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
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