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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Completing sprint leaves the completed sprint in all issues, together with new one

Hi all,

We started using active sprints, and I have a question regarding completing a sprint.

I had an active sprint, let's say "AA Sprint 1", and when it was over I clicked "complete sprint", and under "Select where all the incomplete issues should be moved:" I chose the next sprint, "AA Sprint 2".

The jiras were transferred to AA Sprint 2, but all the open ones still has the old sprint together with the new one - under sprint field I see "AA Sprint 1, AA Sprint 2".

I managed to change it manually in bulk operation, but I was wondering if that's how it supposed to be or I'm missing something in the process.

Thank you in advance!

1 answer

1 accepted

0 votes
Answer accepted
Sandesh Shetty Community Leader Jan 11, 2021

@Idan Klein 

I think it is the expected behaviour. Please find the below screenshot here one issue is currently in sprint 3(active sprint) but same issue was part of 2 completed sprints. So in sprint field it is showing all the three sprints.


It appears that JIRA adds multiple sprints to an issue when it rolls over from sprint to sprint. For example if an issue could not be completed in Sprint 1 and is rolled over into Sprint 2, then JIRA adds Sprint 2 to the "Sprint" field of the issue while also retaining Sprint 1 in the Sprints field. If the issue again rolls over to Sprint 3, then JIRA also adds Sprint 3 as well to the "Sprint" field of the issue, so now the Sprint has 3 values.

Jack Community Leader Jan 11, 2021

Yes this is by design. It maintains the history of where you planned to complete the issue but did not. It ensure historic sprint reports are accurate. 

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,184 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you