How to change sprint in JIRA automation based on name and not id?

[Patrizia Heinzl]

Hello,

I need to change the sprint of an issue with automation.

However instead of using the sprint ID, I want to use the name of the sprint. Is this possible?

Unfortunately below example does not work. I tried a few other things but not sure if its even possible to do this without using the sprint ID?

{ "fields" : {
"customfield_10005" : [{"name" : "Existing Sprint name"}]
}
}

I get the error message: 

Error occurred setting field 'customfield_10005'. It will be ignored. (customfield_10005)

---------------

Info:

I have certain releases mapped to specific sprints.:

e.g

Release name: R23/22 > Sprint name: Sprint R23/22

Release name: R23/23 > Sprint name: Sprint R23/23

> As soon as the release of an issue changes, it should also change to the corresponding sprint.

> Since the sprint has the release in its name, it would be a lot easier using the names instead of mapping each release separately to each sprint ID.

[Bill Sheboy · Accepted solution]

Hi @Patrizia Heinzl 

No, but the work-around for that scenario is to lookup the id needed from the name:

• call the REST API function to get all sprints for your board, using the Send Web Request action
• filter the list by your name, and grab the id for use to set the field

If you want to try that approach, here is a how-to for calling the REST API functions from a rule and the other documentation you will need:

• https://community.atlassian.com/t5/Jira-Software-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

Kind regards,
Bill

[Patrizia Heinzl]

Awesome, that's a great Idea! I will try this. Thank you!

[Mikael Sandberg · Accepted solution]

No, it is not possible to use the name instead of the sprint Id. The reason is that the sprint name isn't unique in your instance, you could have two or more sprints with the same name.

[Kalyan Sattaluri]

Hello @Patrizia Heinzl 

*I am ashamed to suggest this*

Another option,  which by passes API call is to,

create a place holder / dummy story in every sprint which will be discarded eventually.

That way, when release is updated on any story, you can do a lookup of issues in that sprint, which gives you the dummy issue and you can get the sprint ID from that.

{{#lookupIssues}}{{#sprint}}{{#if(equals(state,"active"))}}{{id}}{{/}}{{/}}{{/}}

Which you can use to edit your trigger issue..

/hides