Resolved isn't generally a status like Closed, Open or in Progress. However, setting a resolution is what tells JIRA that the issue is closed. The way to tell if a resolution has been set is to actually set the resolution to anything other than Unresolved.
There are a couple of ways to do this. First, you can have your admin put in a Post Function that will automatically set the resolution to, say, Done when the issue is moved to the Closed status.
The second way is to show the field in either the ticket, or a resolution screen on the transition and set it there. Based on experience, it is better to use a resolution screen that only shows when the issue is moved to the Closed status. Also, it is good practice to have a Purge Resolution Post Function on any transitions out of the Closed status. If you don't, the issue will always show up as resolved.
Does this answer your question?
There's no built-in way to transition issues from status to status, (such as Resolved to Closed) when pressing the Release button to create or release a version on a Kanban Board. I would probably rely on a script to remotely check the version status and then transition the issues in question, in response.
Alternatively you could write a Listener or a Script Runner Listener to achieve this instead via the aforementioned logic.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
@Alice Camilla is a university student, currently writing her MA thesis in Archaeology. She's also a freelance blogger and content creator, writing about geeky stuff from productivity apps to JR...
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