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

Why does releasing a version mark tickets as removed from sprint in the sprint/velocity reports?

Here's the scenario:

  • A sprint (called Sprint 1) showed you had completed 50 story points - this is shown in the Sprint Report and Velocity Report
  • All tickets completed in that sprint are labelled with the same fix version of 1.1
  • In releases, you choose release on that fix version 1.1
  • Once released, you return to the Sprint or Velocity Report and suddenly it shows the there were 0 points completed that sprint.
  • All completed tickets now show in the Issues Removed from Sprint header.

Without this, when looking back at Sprints, it makes it hard (almost impossible) to track progress across sprints in regards to story points completed. 

Hoping someone can help!


1 answer

Hello @Rochelle Driver 

Welcome to the community.

We do not see this behavior in our JIRA Cloud instance. Setting a Version to Released does not automatically change the Sprint field for the issues, and it is the Sprint field that dictates how an issue shows up in a Sprint Report and Velocity Chart. Do you have some custom automation set up that might be doing this 

I'm honestly not sure! I feel its the act of release moving the status from done/complete to closed that is causing the issue. Something to do with the Closed status that removed the sprint tag to none. It must be some customisation somewhere, just can't figure out what! I also don't have full access to all board settings so that might be why I cannot figure out where the error is occurring.

Are you using a Classic project or a Next Gen project?

Suggest an answer

Log in or Sign up to answer

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