Add Ticket to sprint based on the date field

[jan.ambroz]

Hi there, 

We have dozens of pre-planned Sprints, and each of the Sprint have specific date. 

I need automation so that when a new Issue is created this Issue will be added to one of these Sprints based on the date field this Issue has. I found an easy way to add Issue into Active Sprint and Next Sprint but not into future sprints. 

Is there a way to get Sprint ID by the Start and End date of the Sprint in Jira Automation?

Thank you.

[Bill Sheboy · Accepted solution]

Hi @jan.ambroz 

Yes, that is possible...although perhaps not a good idea.  (More on that later.)

To do this your rule would use the Send Web Request action to call a Jira REST API function to gather all of the sprints, filter them to get your desired sprint's id, and update the issue.  I have seen other posts trying this and the complicated part is the filtering.  If you want to try this, here are some references to help:

• https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828
• https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-rest-agile-1-0-board-boardid-sprint-get
• https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588
• https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/

Back to why this may not be a good idea, teams using Scrum use sprint planning to discuss the goal, evaluate work to complete that goal, and confirm their capacity / confidence in succeeding.  Pre-assigning work to sprints this way may discourage a team from the due diligence to understand the work and capacity, and just accept that "the date is the date...get it done".  Please keep these ideas in mind.  Thanks! 

Kind regards,
Bill

[jan.ambroz]

Hi Bill, 

thank you for the response! 

I have one additional question. When filtering web request responses and finding Sprint ID, how can I store this value to use it in the next step?

Thank you 

[Bill Sheboy]

You could either store that in a created variable, or use the filtered value directly.  Here is the Create Variable action for more information: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-variable

Variables cannot be used in all of the different rule actions / smart value expressions.  If it does not work as expected, please post your rule steps so the community can try to help.