We have created an automatic rule to transition certain tickets when we complete the sprint. Here is a picture of the rule:
The idea is when a ticket is awaiting deployment and has the done label once the sprint is completed those tickets are transitioned to the "Done" status and staying in the completed sprint, any ticket in the completed sprint not meeting that criteria will move to the next sprint. The issue we ran into was it moved all tickets in the completed sprint to the "Done" (even the 6 not meeting the criteria) and moved all tickets from the completed sprint into the next one. Any help would be grateful.
Hi @Jason Gaines -- Welcome to the Atlassian Community!
For a question like this, please consider posting an image of the audit log from the rule execution. That may help reveal what is happening. Regarding your two questions...
...all tickets in the completed sprint to the "Done" (even the 6 not meeting the criteria...
The audit log may reveal what is happening with these issues. Somehow they are matching the criteria, or there is something else moving them to Done. Perhaps also check the history for those 6 issues to see how they were moved to Done.
...moved all tickets from the completed sprint into the next one
This is happening because the rule is triggered on Sprint Completed, and so the issues have already moved to the next sprint (or the backlog) before the rule runs. If you want the issues moved to Done *before* the sprint completes, you would need a manually run rule or a rule on some other trigger, such as scheduled for the last day of the sprint.
"No", and that doesn't matter for your use case. You may trigger a manual rule from a specific issue, and within the rule you could use a branch on JQL to process what you need to take action on.
Yet you were trying to automate this to save time, prevent errors, etc. That is one reason I suggested the Scheduled trigger rule. It could run on the last day (or even last hour) of the sprint and use JQL to select the issues with the criteria needed to move them to done.
Do you deploy only on the last day of the sprint? Is that why you wanted to wait to move those issues to Done?
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
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