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

To generate sprint report is it necessary to close the sprint

Hi, as working as scrum master I want to generate the sprint report but when we go to the new sprint we usually take some days to clear the tasks etc.. from our previous sprint so I am bit confused if that affects the report of that previous sprint because I have already started the new sprint so I dont think the report will be affected of the old sprint.

all suggestions are welcome.


1 answer

1 accepted

0 votes
Answer accepted

Hi @Jasmin Laroche 

The Sprint Report will be available from the start of a sprint - and will continue to run and record actions until you close it (even if the end date has passed).

It would only impact the new sprint if you had moved an issue from the previous sprint into the new sprint - otherwise, it would continue to display against the previous one.

I would suggest this isn't good practice though - a sprint is a timebox, and should end on time. I would:

  • Ensure the team is moving stories to "done" throughout the sprint - to reflect the actual completion rate (impacts burndowns, etc)
  • If you reach the end of a sprint and a story is not complete - close the sprint, and roll the story into the next sprint
  • Do not remove stories before you close a sprint - you want to see completion vs incompletion in your reporting. Removing a story will show it as "removed" not "incomplete"
    • This will also allow you to search for issues which are in closed sprints and open/future ones, and use your retrospective to discuss why a story was not possible to complete within the timebox

You want the data to reflect both success and failure, so you can find where your team needs to improve every sprint.


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