How to Get NextSprint through Special Value or JQL for JIRA Automation.

[shantanu behera]

I am intending to set up a JIRA Automation to check if the Sprint of an issue has been updated for the currently running sprint or for the next upcoming sprint. Whenever an user does that, I'll add a comment or label so that those tickets can be picked for Grooming and Estimation ASAP. Can anyone suggest how to get the nextsprint name/id either through special value or JQL?

[Bill Sheboy]

Hi @shantanu behera 

The challenging part in what you describe is identifying the "next upcoming sprint".  I suggest separating this into two things:

• Use a rule to detect the sprint scope change for issues added to the in-progress sprint.  Although...the team and Product Owner should already know that when the team is collaborating as someone will immediately notify others, possibly doing so at the next Daily Scrum / Standup.
• Use normal backlog refinement practices to identify work in upcoming sprints, without using an automation rule

If you still want an automation rule to identify both the sprint scope change and the upcoming work, the solution suggested by @Nikola Perisic will work if you have one-and-only-one upcoming sprint.  Otherwise...

When you have multiple upcoming sprints in Jira AND they have their Start Date field filled in, a rule could call the REST API endpoint with the Send Web Request action to get all future sprints for the Jira board.  Then it would identify the one with the minimum Start Date (i.e., the earliest one).  Finally, it would use that date to create a regular expression to search the sprint list to identify the sprint's ID, testing that to compare with the issue's sprint field.

Kind regards,
Bill

[shantanu behera]

Hi @Bill Sheboy @Nikola Perisic Appreciate your response. Yes, I am explicitly looking for a JIRA Automation rule to implement so that even if it's missed a comment will be logged in the ticket comments.

I already tried the approach which @Nikola Perisic had suggested but the issue is if I have multiple upcoming sprints (futureSprints()), then it'll consider all of it. How ever, my purpose is to check if a ticket which has been marked for the next sprint should not have a blank / empty Original Estimations. 

[Bill Sheboy]

Thanks for the additional information!

Your rule could first test if the Original Estimate is set, and if not only then use the REST API to check the sprint values (for upcoming sprints).

[shantanu behera]

I tried the approaches to create my JIRA automation as per the suggestions. However I found the easiest way to tackle this situation is by just naming the next sprint in the board as "Next Sprint" and then use a JQL condition

Sprint IN (OpenSprint(), "Next Sprint")

Of course, this is not the ideal way but is just a work around to get the desired result.

Thanks @Bill Sheboy and @Nikola Perisic for your suggestions.

[Nikola Perisic]

Hello @shantanu behera 

You can make something like this:

 

for project put your project key instead the one from the picture.