I had set the automation for Resolution as Done. After configuring this automation, my User Stories are resolved as Done when I change to appropriate status. Whereas the Resolution are not changed to Done if I do manually for the past User Stories.
I have written an automation for setting Resolution as "Done" for unresolved tickets in Resolved Status. Also we need to make sure the Resolved Status tickets have edit access for this rule to run.
Please see the image attached. Automation ran successfully and resolution was set to Done.
Note: The cron expression to be written for UTC timezone. to build a cron refer this link
As a recommendation you can run the automation as single project so that it doesn't consume the global automation rules.
Hope this helps.
There are two parts to this question.
First, the setting of resolution is important in Jira, and you've done it with Automation at the right time. However, that is clumsy, unnecessary, and hard to maintain. The best place to set a resolution is in the workflow, as Jira does by default. You can do it with post-functions, or with a resolution screen on the transitions.
You'll also need to maintain an automation that clears the resolution when you re-open issues (again, also better done in the workflow, with a post-function to "clear resolution")
I've talked though this because it frames the second half. The important thing to note is that with automations, post-functions or screens, the resolution is all being set when an issue istransitioned.
So, second, once you have fixed your workflow/automation such that it sets/clears the resolution on issues at the right time, you still have a pile of historic issues with no resolution.
You will need to get these updated somehow. The obvious way to do it is to re-open and then re-close them, as that will trigger the resolution setting as above.
You could also try a "bulk edit", but you'll need to be very careful with that, as you have to put the resolution field on the edit screen to enable it, and if someone edits an issue while it is there, they may resolve issues that you don't want them to.
Your last option is some scripting, if you have one of the scripting apps (Scriptrunner for example, has a built-in script for repairing resolutions when a workflow has been broken), and I think it may be possible to set up a one-off automation that can hit a range of issues.
To set the value for existing Done issues, you will need to edit the workflow and create a looping transition on the Done status - that's a transition that goes from the Done status to the Done status. I usually add a condition that only Jira Administrators can execute that transition.
Then add a post function to set the Resolution to Done - just like you need to add to any existing transitions to Done in your workflow. Be sure to Publish your workflow!
Then write a filter to view all of the issues on that project that are in the Done status but the Resolution is missing: project = ABC and Status = Done and Resolution is empty
Then do a bulk change on all of those issues and select Transition Issues
Then transition the issues using this new looping transition you just added to your workflow.
You will need to add a "Post Function" for resolve transition to Set Resolution as Done.
When your issue is now moved to Resolved the Resolution will be set.
But for older issues you may have to write a automation schedule rule include JQL there and set Resolution as Done
Hi @Vishwas N M Thanks for the swift reply.
The first is done and its working. Whereas the second part i.e., for older issues, I'm trying to figure out what needs to be done.
It'd really helpful if you could share any examples of reference links to refer to.
Hi everyone! Are you interested in beta testing Atlassian University’s newest (unreleased!) training course? We’re looking for 15-20 volunteers to test our newest training course, Basic reporting...
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