Or, and what I typically elect to do, add a Validator to require the resolution field to be set by the user transitioning the issue to Done. You will need to also add a screen to the transition with the resolution field. The reason I prefer this most of the time is that I like to be able to reflect on the different reasons an a issue is considered done, e.g. done, won’t do, cannot reproduce...
This should help.
Hi @Magic Mike ,
I am facing with a similar situation here. The Resolution field is empty, so that the closed / resolved / unresolved issues are stuck "in progress", and cannot transition to "close". A legacy automation was created to transition an issue to "close" after 3 business days if the issue is "resolved".
For past issues associated with this workflow, how can I update the "post-function" or the value of "Resolution" in them?
Is it possible to bulk change the values in this "Resolution" field?
Thanks a lot!
Consider editing the workflow and adding a temporary loop transition from done back into done or whatever you’re done status is. On that transition add a post function to set the resolution. Publish the workflow and then use bulk edit to transition all of the issues in the done status without resolution using this transition.
Hi @Jack Brickey ,
Thanks for your answer!
Please correct me if I am wrong, for future new issues, they will transit via the post-function - updating Resolution field and then be resolved? In this manner, I assume they will no longer displayed in the report as in progress?
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