I am currently unable to find a simple solution that would allow me, a Jira Admin, the ability to remove or reset the resolution field.
Currently, when a jira user accidentally sets an issue to a status of 'Done', the resolution field is also set to 'Done'. Once this happens it cannot be removed/reset. Even if the user moves the issue back to a status of 'To Do' or 'In Progress'. This seems to only affect a company-managed project.
I am aware that I can make the resolution field apart of the screen scheme and can be edited by a user by selecting an option from a drop-down but that is not what I want. As a user, I want to be able to move an issue out of a done status and the resolution field to be removed/reset (aka: no longer visible) when I move it out of this type of status.
To clear the resolution field on an "In Progress" or "To Do" issue you can create a post-function on each transition of the workflow that is supposed to "clear" the resolution field.
This article can give you some ways to implement that Best practices on using the "Resolution" field
I hope it helps. If this answer helps solve the problem, please come back and mark this answer as solved to help other community members with the same challenge. If not, you are welcome to share your solution as well.
Cheers,
Alex
What Alex has conveyed here is precisely what you want to do on your workflows when transitioning out of a done status category. This will ensure, going forward at least, that your resolution is properly cleared when you reopen an issue.
However, to clear existing resolutions on issues that are not in a done status category you would want to implement a temporary loop transition and apply the post function to clear the Resolution field on that loop transition. A loop transition is one that exits and reenters the same status. what you can do once you have that temporary transition in place is to perform a bug edit and transition all issues that have the resolution stuck. Once that is all out of the way you can simply remove that temporary transition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This leaves a lot to be desired. Why not a 'clear resolution' action, or 'Reopen' action, or heck, just give us a 'Clear' option when added to a screen for editing?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would very much like to see the Resolution field be fully editable like any other field, including clearing its value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just create automation on transition from Done and set the Resolution to empty in JQL?
This would mean anyone even dragging it back from Done to "To-Do" or "In Progress" would trip the automation and there would be no Resolution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just implemented Marc Isikoff's "Automation on transition" suggestion. Worked perfectly.
I just needed to create a simple automation called "Clear Resolution" on the "Issue Transitioned" trigger to "Edit issue fields" for setting "Resolution" field to nothing (ie. don't select any value from the dropdown).
To fix the already affected issues, I created a new "Paused" status ("In Progress" type) just so that I had a status to bulk-move all the affected tasks into temporarily (to cause the above automation to run), before bulk-transferring them back to their original status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Regarding the Automation route be sure to consider the global/multi-project limitations of Automation if you are on Standard/Free. Whereas the Workflow solution does not come with limits, Automation does. For Automation you can avoid the limits by copying the rule and applying to each individual project rather than global.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
NOTE: Jira does not allow setting the Resolution field to "None" directly in Automation. Leaving it blank did not work for me as the Automation rule failed.
However, you can clear Resolution using an advanced Edit Issue action with JSON.
Set the below in the Additional fields (More Options):
{ "fields": { "resolution": null } }
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.