Please, do not say "resolution status". Resolution and Status are totally separate things.
The problem you've got here is that you've customised your workflow and removed the things that were setting the resolution field when you get to the end of an issue's lifecycle.
Have a quick look at the default JIRA workflow, as it's a good stable example. In there, the users have decided that both status of "resolved" and "closed" should be "ended", and hence, if you look at the transitions into those status, you will find that they have a Screen that contains the resolution field, which means the user is asked for and always sets a resolution. (You can also do that with a post-function if you don't want to ask the user for a resolution). On the way out of those status and back to any of the others where an issue should be "unresolved", you will find a post-function that says "clear the resolution field".
You need to do the same in your workflow.
It's a bit of a hangover from JIRA 1, and something I've always thought was clunky and needed changing (I'd group status together into meta-status, rather than a simple open/closed)
A post-function is a workflow artefact - it's "something to run when a transition executes". There's a standard 5 of them added to transitions by default to do things like fire events, update the index, save the issue etc, but you can add your own. Including set/clear resolution.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
An efficient enterprise content management system, or ECM, is a must-have for companies that create work online (cough cough, all companies). If content calendars, marketing plans, and bu...
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