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; } } }

Velocity Report broken

Sven Horner

We just started Sprint 10 with our new board, but the Velocity report looks like this:

Bildschirmfoto vom 2024-05-28 14-20-16.png

For Sprint 6 and 7 the Completed column is not correct, for Sprint 8 and 9 both the Commitment and the Completed column are incorrect.

We found some recommendations on the forum to close the sprint and start it again, that didn't help. Also it was recommended to revert changes like adding a new status. As it stopped working a while ago, we can't exactly tell what the changes were. So that doesn't help much either.

But as you can see, there are some changes in the Story point estimate field registered in the Burndown chart report, here in Sprint 9 for example:

Bildschirmfoto vom 2024-05-28 14-26-51.png

It really seems there is something broken with this report.

Accepted answers

All comments

Vasyl Krokha _Broken Build_

Hi @Sven Horner

Can you share a sprint details screenshot with issues? All the details can be hidden except statuses and estimations. Also, can you share your Scrum board columns to statuses mapping the board configuration?

All built-in Jira reports are calculated on the fly, so all configuration changes are considered once they are made. The completed metric depends on which statuses are mapped to the last board column. Most probably, the issue is related to how this item are configured.

Regards,

Vasyl

Sven Horner

Thanks for offering your help, Vasyl.

We think by Scrum board columns to statuses mapping you meant the following:

Bildschirmfoto 2024-05-28 um 16.42.42.png

For the first one we weren't sure what you would like to see. Can you please clarify?

Thank you,

Sven

Danut M _StonikByte_

Hi @Sven Horner,

You could to open a support ticket with Jira's support team and ask them why this happens.

Also, a better alternative to this Jira report would be the Team Velocity gadget offered by our Great Gadgets app. It is more advanced, works with any type of estimates, can count sub-tasks, offers additional metrics (like scope change, added or removed) and a Data tab with a detailed info about the issues from each sprint. It works differently than Jira report, so I expect to display correct data.

You could start with a 1-month free trial. If you have any questions, feel fee to contact us at support@stonikbyte.com.

Hope this helps.

Danut.

Vasyl Krokha

Hi @Sven Horner

Thanks for sharing the column mapping.

The second part I asked about is Sprint details. In the Velocity Chart you showed earlier there is a list of completed sprints, if you click any sprint you will get sprint details report which includes burndown and list of issues grouped by categories: completed, not completed, added, removed like below.

When we investigate such issues we this chart and list of issues. You can see status, estimation. Together with columns mapping this could give a hint on what is going on on a ticket level. E.g. you take a particular ticket which you thing is not done, but you thing it should be in Completed issues list.

Screenshot at May 29 08-57-01.png

Sven Horner

Hi @Vasyl Krokha,

thank you for your reply. Unfortunately in our case we can't click anything in the velocity report. Are there maybe different types of projects?

The closest thing we find is under the route /jira/software/projects/ITX/boards/XX/reports/burndown, or Reports -> Burndown, where we can select past sprints.

Here, with the sensitive fields cropped, it looks like this in the list below the actual burndown chart:

Bildschirmfoto vom 2024-05-29 09-36-26.png

This doesn't inlcude the status unfortunately. It's not the end of the list, there were about 4 times more in this sprint.

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