Automation rule - Setting sprint value to 'next sprint' when current sprint is not the active sprint

Idan Har Even

Overview
During grooming of sprint X, stories that require automation development are marked with a custom field that determine if an automation task needs to be created or not. Tasks that are created during this process will be developed on sprint X+1. 

 

Problem 
When trying to define a rule to move created task to sprint X+1, Jira only allows me to select 'next sprint', however 'Next sprint' is actually sprint X according to Jira as it adjacent to the active sprint.

Sprint X is a future sprint and the task is eventually not moved because Jira finds that it is it already in 'Next sprint'...

Is there a way to acheive this without having to specify to which sprint the task is intended for?

 

 

 

Bill Sheboy

HI @Idan Har Even 

No, that is not possible based on the use case you have described.

You describe refining work for the "next sprint", and there is currently no built-in way to select the sprints after that...relative to "next"...from the rule.

If your sprints have a predictable naming convention, it would be possible to determine the upcoming sprint's id (and so make the assignment) by calling the REST API from the automation rule and then filtering by your target sprint's name.

Kind regards,
Bill