I recently changed our workflow (using Jira on Demand V6.2) to include the following steps: Open >> In Progress >> Code Review >> AC Review >> Done. We were using Jira's Simplified Workflow, but wanted to insert the Code and Acceptance Criteria Reviews. Since I made that change the Resolution field (Status) is causing every issue to be resolved when any update is made to the issue. As simple as adding Story Points will cause the issue to be marked (crossed over) as "Resolved". The resolution label does not affect the behaviour at all. If I hide the Resolution fielf the problem goes away, but then we cannot tag issues as "Resolved".
There is no way for me to change the Resolution from Required to Optional. Also the issue stays "Resolved" even if I close it and Re-open it. NOTE: nI also have tried changing the final step to "Close" instead of "Done" and it has no effect on the problem.
Help. I am at a lost, anyone can suggest how to solve the problem? Is it a Issue Screen setting? Is it a Workflow Screen setting? Any help will be greatly appreciated. Thx. CD
First, check that you have not got "resolution" on any screen where you do not want it set to something (it should only be on the view screen, and screens that go into status where you want a resolution set. It must not be put on create, edit or most transition screens)
Second, check the workflow for set/clear resolution post functions
Third, check your listeners for something that might set it.
(I suspect it's the first one though)
Can you have a look at the workflow transitions, and see if there are any post functions present which will change the value of the resolution field? If these are present, you should remove them.
Whenever the resolution of an issue is set, it will get interpreted as being resolved, and there for it will crossed through
Again, thank you for your help.
As it turns out, I was never able to pin point to the culprit "screen". However, your answers helped me solve the issue, by deleting all the automatically created screens (every time you create a new project) as well as screen from old workflows. I also deleted the resolution field from the issue form. And then lastly, I created a post function that Resolves issues when the move from "Review" to the "Done" state. The workflow now works as expected.
On the problem of Issues which were "crossed-out" as Resolved, but had not even been worked on; I had to clone them into new issues and then delete the ones that were crossed-out.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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