I would like to check that the resolution field is not set to unresolved before a story is being closed. I was wondering if there is a way to do this to prevent unresolved items from being closed.
You can choose the "Value field" workflow condition and checked for Resolution != "empty string here".
Having said that, I would prefer an option close items that are unresolved because you might be closing tickets because they are duplicate, invalid etc. It doesn't make any sense to Resolve them first and then close it.
However, if your business process requires that, value field condition should work.
Add the Resolve issue screen to all transitions to Closed in your workflow.
To do so, edit the workflow, click on a transition to Close, and add a screen through the option in the right side.
Repeat the process for each other transitions that may go to Closed, and finally Publish your draft.
Besides, you can create some new resolutions to cover cases in which issues are closed without actually been successful: Won't do, Won't fix, Out of scope, Duplicated, Invalid... or whatever.
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