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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • 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

Velocity chart not showing work completed Edited

Hi,

I've just been informed by one of our project managers that our Velocity Chart is "no longer working"!

I think this has come about as a result of my modification of the board and workflow, which I'm trying to prepare for future Release Notes automation.

Specifically, I added a new 'Merged' column to the board (after Done), to allow us to differentiate between code/features that have been completed and those that had then been merged into the main branch, with a transition from DONE to CLOSED.

Unfortunately, this caused another issue for me yesterday afternoon whereby ~698 issues were returned on to the backlog, which I resolved by performing a Bulk change of all issues with a DONE status AND not in current sprint, to CLOSED. This worked for the backlog, returning the number of issues back to what it should be.

However, this has caused another problem with the Velocity chart, which no longer shows the 'completed' work for issues in the past few sprints. Looking at the affected sprints, I can see the status of the issues is DONE, but when I look in the Issue Navigator the exact same issues status are CLOSED.

I suspect that the Velocity chart requires the issue status to be CLOSED, but since the affected sprints have been completed that their status was 'as of' the time when their sprint was completed.

Could you please let me know how I can resolve this, since I'd like to show the actual work completed.

Thanks

2 answers

1 accepted

0 votes
Answer accepted

Resolved this by re-opening the sprint and closing it straight after.

I recently experienced this for the first time. Turns out the Scrum Master re-arranged the board's columns on which the report was based, adding two new statuses after "Done."

Once those columns were removed and the board was re-configured as it was originally set up, the completed bars started re-appearing in the Reports.

Takeaway: Don't add statuses after "Done" 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Agile

On-demand: Fireside chat with Atlassian on scaling agile organizations

Scaling an agile organization and setting it up for success over the long term is a hard thing to do. We hear a common set of questions from customers all the time, questions like: Can agile scal...

3,877 views 2 17
Read article

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