I edited the title of an issue and I think it set the resolution to FIXED as a side-effect. I blame resolution being a required field in the edit dialog, and not offering to perpetuate the unresolved state.
I read this post looking for a solution: https://answers.atlassian.com/questions/1765/how-do-i-set-the-resolution-of-an-issue-to-unresolved ...but it wasn't very helpful. I tried closing and reopening the issue, but that didn't help. I am loathe to invest the effort into understanding the whole post function discussion... it seems geared for setting up a workflow instead of just fixing a bad field.
Can someone please just provide a step-by-step to set this one field on one instance?
The 'unresolved' state is triggered by the field being empty in the database. You need to pass the issue through a transition that uses the clear the field post function on it. The resolved field should never be on screen except the transition screen shown when you are in a step in the workflow where it must be set. It will automatically appear on the issue screen.
Resolution is an unusual field in that it is only expected to be placed on screens that are used in transtions that end in a status that you want to count as "issue is done with". Exactly as Joe says, you must not place it on any other edit/update screens, otherwise it will be set accidentally.
Gary - Same issue here. And similarly I am hesistant to engage in post-function processing.
This seems to me a major Jira limitation. If adding the field to the edit screen is going to wreak havoc, then adding the field to the edit screen should be disallowed.
I've since reverted the change, but for the tickets that were marked with a resolution during that timeframe, I have no recourse to "nullify" the errant tickets.
As a result, tickets which are assigned to developers, architects and techincal resources are not surfacing in their "Assigned to Me" dashboard, and work is being missed.
Would love to see Atlassian put serious effort towards addressing what many folks have discovered to be an egregious pitfall ... easy to fall into, difficult to get out of.
Gary - please let us know if you come across a straightforward solution.
The solution for fixing your damaged issues are
It might seem like a limitation, but it begs the question "why are you editing a resolution, when the fact it's resolved means you don't care any more?"
But "undo" is a luxury, and should be unneccesary. The way Jira handles resolution was suitable in version 1 and arguably 2, but it's not worked well since version 3. It needs to change.
But this is the way it is now, and this is how you have to deal with it. Until Atlassian grasp that nettle and fix the way resolution/done/open/closed works properly.
It does. I'd junk the "resolution" approach completely and fix it properly myself. But it's deeply ingrained in JIRA and apparently the Atlassian psyche.
If you have the script runner add-on, there's a canned script for fixing the issues that got broken by inappropriate usage of the field though.
The resolution should never be on ANY screen except a transition screen presented when you want it set. It is ALWAYS required whenever available for update. To clear it you need to run the issue through a transition with a post function to CLEAR the field. The UNRESOLVED shown in red really means it is null.
Cycling back through the workflow does not allow me to set the resolution to "Unresolved". That is not an option in the drop down. And I cannot clear the resolution - it's a required field. So what to do? This ticket was abandoned in error and needs to be brought back. I cannot use the SQL option because I use Jira on demand.
Yesterday I found a simple solution to this that worked for me.
This is basically covered above by @Nic Brough [Adaptavist] in JIRA speak (not a criticism) as 'Push them back through the workflow so that a "reopen" transition somewhere blanks it out'.
On a Kanban board I moved the trouble issue back to the "To Do" column and it reset the resolution to "Unresolved".
I would testify in court that I've tried this several times before and it didn't work but that may have been on an Agile board.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot