We have several teams that are sharing a workflow, but one team wants to fill in the Resolution field during an earlier transition than another team (who will fill out this field before moving to "Complete"). Is there any way to have multiple points at which a resolution can be chosen? Because this field is required any time its placed on a screen, I'm not sure how to make it optional at an earlier transition (or edit screen).
I have already looked at the following thread about Resolution field being required:
I'm afraid not.
The field isn't actually "required" in the sense that other fields are. Most required fields are an explicit "this is required, you can't commit this data without it". Resolution is not required at all, but it doesn't have a "leave me blank" option, so as soon as you put it on a screen, it is filled in. I suspect that if you hacked the field code that renders it so that you did have an empty option, you'd find it works the same way as all the other select lists (and then everyone would have to use a validator to make it mandatory on all the resolve transitions)
It's a bit of a hangover from very early versions of Jira, but there's no way to change the behaviour without coding.
The only way I've gone around it is to have explicit "set resolution" transitions for when it's needed earlier in the workflow.
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