nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to move an issue to next sprint using automation rule while retaining the old sprints

Swetha Balasubramaniam

I have created an automation rule that creates the new sprint for every week.

I am filtering incomplete issues of previous sprint to assign it to the new sprint that i have created now.

I am able to filter issues. But not able to assign new sprint while retaining the old sprints(history of sprints).

Is there a way to keep old data and also assign the new sprint? Please LMK

Accepted answers

All comments

John Funk

Hi Swetha - Welcome to the Atlassian Community!

When you move an issue from one Sprint to another, it should update the history for that issue. After it is moved, just go down to the Activity section of the issue and click on History.

Karan Sachdev

Hi @Swetha Balasubramaniam

Welcome to Atlassian Community!

If you move the incomplete issues to the next sprint when the current sprint is completed, then the previous sprint values are retained.

However, if you update the Sprint field via automation, the current sprint will be removed and the new one is added. It will still hold any previously closed sprints that it was a part of.

Example, You complete Sprint 1, and incomplete issue (JIRA-1234) is moved to Sprint 2. Now while the sprint 2 is active, you run an automation rule to update it to Sprint 3, the issue will show Sprint 3 +1 (which is the previously closed Sprint 1).

Thanks!

Swetha Balasubramaniam

Hi @John Funk ,

When we manually close a sprint and move issues from this sprint to next sprint, we could see issues in the newly created active sprint.

In the sprint field of these issues, we could also see how many sprints these issues have been through. Pls refer to the screenshot attached.

Screenshot 2025-04-14 at 8.01.59 PM.png

But, while we update sprint value for an issue from Automation rule-> Edit Issue-> Advanced fields using below payload,

{
"fields": {
"customfield_10020" : {{createdSprint.id}}
}
}

it replaces the entire list with a single sprint ID and previous sprint details are lost.

Pls refer to the screenshot attached.

Screenshot 2025-04-14 at 8.16.59 PM.png

Is there a way to replicate what happens during manual sprint movement in automation rule as well?

Swetha Balasubramaniam

Hi @Karan Sachdev ,

When we manually close a sprint and move issues from this sprint to next sprint, we could see issues in the newly created active sprint.

In the sprint field of these issues, we could also see how many sprints these issues have been through. Pls refer to the screenshot attached.

Screenshot 2025-04-14 at 8.01.59 PM.png

But, while we update sprint value for an issue from Automation rule-> Edit Issue-> Advanced fields using below payload,

{
"fields": {
"customfield_10020" : {{createdSprint.id}}
}
}

it replaces the entire list with a single sprint ID and previous sprint details are lost.

Pls refer to the screenshot attached.

Screenshot 2025-04-14 at 8.16.59 PM.png

Is there a way to replicate what happens during manual sprint movement in automation rule as well?

John Funk

Try updating the Sprint field using JSON instead of just using the native Sprint field:

{

"fields": {

"sprint": [

{

"id": "your_sprint_id"

}

]

}

Swetha Balasubramaniam

@John Funk

This is throwing the following error,

(Number value expected as the Sprint id., The Sprint (id) must be a number (customfield_10020))

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud