Earliest future sprint using JIRA Automation

[prasanna Subramaniam]

Dear Community,

Is there an option to get the earliest future sprint using JIRA Automation under a specific project.

Thank you!

Prasanna Subramaniam

[Walter Buggenhout]

Hi @prasanna Subramaniam and welcome to the Community!

I am not sure what you are trying to do, but if your idea is to use automation to assign issues automatically to the next upcoming sprint, you might be able to do so with the Edit Issue action. Select the Sprint field and from the option list select Next sprint (name of the scrum board).

Hope this helps!

[prasanna Subramaniam]

Dear @Walter Buggenhout ,

Thank you for your input. Below are the details of what I am aiming to achieve:

I want to automatically create a couple of sub-tasks and assign them to specific resources for the user stories tagged to the earliest future sprint, 2 days before the sprint start date.

Is this possible ?

[Atlass Monster]

I think the solution will involve REST and Web Requests.

Gather a list of all future Sprints. You will be able to tell which is the oldest by checking if the json answer have array value of 0. You will need the id of the sprint, store it as variable.

Link: https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-rest-agile-1-0-board-boardid-sprint-get

Check the Sprint data if the end is 2 days from now: https://developer.atlassian.com/cloud/jira/software/rest/api-group-sprint/#api-rest-agile-1-0-sprint-sprintid-get

You will have to perform date value difference comparison: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/

Given the name of the Sprint from the rest api GET request, use it in a JQL lookup issues to get all Stories with {{MyFoundSprint}} value. 

After that you can loop the issues and perform the actions you need.

[prasanna Subramaniam]

Thank you @Atlass Monster for the response. Will look into this option.

Any other Option without REST API

[prasanna Subramaniam]

Dear @Walter Buggenhout  , Could you please share me more information on the option that you metioned.

[Walter Buggenhout]

Your use case is still slightly vague to me, to be honest. If I understand correctly (and I am really starting to make assumptions now), you have defined a couple of stories for an upcoming sprint and just before the sprint is going to start, your plan is to automatically break down (some? all?) stories into subtasks that you then assign to separate users / teams to work on.

I am not sure if you are trying to automate the right things here, nor if you are automating them at the right time.

If you know you are going to break down your stories into sub-tasks, why don't you just create them immediately when you create the stories? Of why don't you create them at the sprint start? Since there is no trigger in automation for 2 days before the next sprint starts, you could easily solve the problem of having your sub-tasks created with an easy to use trigger (issue created for my first option, or sprint started for the second option).

Everything else you mention in your scenario (assigning the issue to resources, adding them to the sprint), is essentially nothing more than filling out fields on the sub-tasks being created. 

[prasanna Subramaniam]

Dear @Walter Buggenhout , 

The sub-tasks I mentioned are intended for the Solution Architect team to review and approve, and they prefer to get it assigned and complete them only 3 days before the sprint start date.

[Walter Buggenhout]

Are they performing the review and approval before or in the sprint, @prasanna Subramaniam?

[prasanna Subramaniam]

Solution Arch review and approval before the start of the Sprint. 

[Walter Buggenhout]

Ok, so it doesn't make much sense to add those sub-tasks to the sprint then, does it - as the activity is happening outside of the sprint?

Assuming that your sprints are on a fixed cadence, have you considered simply setting up a scheduled automation rule that runs with a fixed cadence as well, 3 days before the regular sprint start and creates - maybe even just 1 - task(s) for the SA Team to perform the pre-sprint review?

That would eliminate a lot of your complexity and alert that team that it's time for the review.