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

[Ponce de Leon, Eduardo]

Hi @Bill Sheboy as of Feb 2025 is there still no way to search for stories that are defined in the next sprint?

[Bill Sheboy]

Hi @Ponce de Leon, Eduardo -- Welcome to the Atlassian Community!

Short answer: not with built-in features of JQL.  There are likely marketplace apps / addons to JQL to add that type of search for sprints.  

There are some very old suggestions to add this capability to JQL:

• https://jira.atlassian.com/browse/JRACLOUD-72007
• https://jira.atlassian.com/browse/JSWCLOUD-15265

The closest thing with built-in JQL would assume one knows the next sprint's name:

project = myProjectKey
 AND sprint IN futureSprints()
 AND sprint = "my next sprint name"

The more complicated approach is the one I noted two years ago: dynamically build / update a saved filter to find the issues in the next sprint based upon the dates.

Kind regards,
Bill

[Ponce de Leon, Eduardo]

Hi Bill, thank you for your reply.

I think what is making it hard is that the team has 2 or 3 future sprints so, this makes it hard.

Sprint names are alwyas with the same name 

Sierra Spr32: 5/Feb - 18/Feb

Sierra Spr33: 19/Feb - 4/Mar

Is there a way to search if I am currently with sprint 32, to search only for sprint33 items since the sprint is not a text field

 I would need to add 15 days to a variable, can I do that with variables?