I am experiencing an issue with the Complete Sprint Automatic rule I created.

Question

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.

Bill Sheboy · Answer

Got it.  I'd recommend trying the manual rule for a sprint or two, see if that works for the team, and then decide if you want to fully automate it on that last sprint day.

Jason Gaines · Answer

Bill,

Yes, deploy on the last day of the sprint.

Bill Sheboy · Answer

Hi, Jason.

"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?