Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Set sprint ID using advanced JIRA Automation

I am trying to set sprint id using JIRA automation to assign a card to a specific sprint in the future that isn't the "next sprint".

I have found sprint ID by going to to /rest/api/2/issue/<issueNumber>?expand=names, as well as inspecting element in dev tools. I have also confirmed customfield id for Sprint.

This is the advanced JSON I am using:

"fields": {

And this is the error I am seeing in Audit log:
Error editing issuesCRM-10274 (Number value expected as the Sprint id.)

Any ideas as to why I am getting this error?


2 answers

1 accepted

6 votes
Answer accepted

If anyone gets stuck on this in the future I figured it out...

"fields": {
"sprint": 275

if you need to assign a text value in another field (like a text customfield), you may use

"fields": {
"customfield_10001": "xxx"
Like # people like this
0 votes
Deleted user Oct 06, 2021

I was unable to get the 'Single-select custom field' working according to this article.

I ended up re-purposing an old sprint we no longer used.

"fields": {
"sprint" : 3

If you need to create a Story and assign it to a Sprint based on user input (say in Jira Service Management) it's as easy in automation as copying from triggering issue. No need to get it's ID vs it's value.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events