In a properly configured Jira, there is no way to do this.
The reason for that is that a properly configured Jira
However, it is possible for inexperienced admins to get point 1 wrong, leaving you with closed issues that are not closed because the resolution is empty.
So the complete fix:
Based on the number of people who have asked this question, Atlassian/JIRA should really consider adding a "edit closed" screen that does allow you to change the resolution.
In the meantime, here's the workaround I've used for individual issues marked with the wrong (or a missing) resolution. For what it's worth, most of the missing resolutions are due to closing an issue in the mobile app - the app doesn't seem to enforce the required resolution field.
1. Click 'Edit' on your issue
2. Click 'Configure Fields' on the top right of the resulting pop up screen
3. Click on 'Where is my field' if you don't see Resolution in the field list
4. Type in 'Resolution'
5. Now scroll down to the 'Field Screen' section. There will be a message explaining that the Resolution field is not included in the screen configured for this issue. There will be a link to the Screen Configuration settings page. Click on that link.
6. Add the Resolution to the Screen Configuration page. Keep this page open (you will remove the new field from this configuration shortly).
7. Navigate back to your issue and click 'Edit'. Now you should see the Resolution field as an option. If it's still missing, you may need to select the Resolution Field in the 'Where is my field' dialog to see it (you also may want to try refreshing the browser).
8. Once you can see the field, update your resolution to the desired status. Click 'Update' to save.
9. Finally, return to the Screen Configuration page and hover over the Resolution field. Click 'remove' when it appears on the right.
This process essentially adds Resolution to the 'edit' screen temporarily. If you leave it on permanently, and it's a required field, you won't be able to move from Unresolved to another workflow phase.
Again, I think Atlassian/JIRA should come up with an easier way to edit the resolution on closed tickets, but this will help in a bind.
Thanks for the tip - huge help!
I've been careful to set up Resolution correctly in my workflows. A few months later had to remove a status from them, due to business process change. When I published the revised workflows everything that used to be in the (now removed) status got set to Done. That resulted in a heap of issues in "Done" without any resolution. This tip helped me fix them quickly - saved me having to edit all those workflows again!
Hello @Marzi Goodarzian and all,
I had the same issue and apparently the below solution worked for me:
e.g. with label "jira_resolution_manually_set"
There are 2 drawbacks:
You might find this solution a little bit simpler than the one suggested by @Nic Brough _Adaptavist_. Or not :-)
Yes, I believe you can, search for desired issue or issues, click tools on your right -> bulk edit -> edit issue or transition not sure which at the moment don't forget to uncheck the box "Send mail for this update" o you can leave it checked whatever you desire.
If your issues are unresolved, copy or edit your current workflow add a new status in workflow after Done add a post function to it witch sets the issue resolution to resolved, use bulk edit to correct the mistake, after correcting the mistake edit the workflow back to its original state or if you copied it and edited the copy switch back to original one.
Also to avoid future mistake check your current workflow, you need to add a post function before Done, post-function which will change the resolution of the issue to resolve.
If you want to reopen all your issues, you have to add a transition from Done to Open and call it Reopen and add a post function which changes the resolution from resolved to unresolved and then you can bulk edit.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events