Velocity Report broken

[Sven Horner]

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

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:

It really seems there is something broken with this report.

[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:

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

Thank you,

Sven

[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.

[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:

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

[Sven Horner]

Oh wait, @Vasyl Krokha I found something. Further down, we also have a section that says "Completed issues"

We have an automation that sets the Story Point Estimate to 0, as soon as the ticket is in status "On Staging". This was done to have it burned down in the burn down chart. Apparently that's not how it is supposed to work. So Sprint 9 looks like this (that looks more like the Sprint details you requested):

We have closed our current sprint with a test ticket that still has a Story Point Estimate of 16 but is Done, now we have something in the Completed column in the Velocity Report.

What we still could not solve is, why the commitment is also 0. The issues which where moved to the new sprint still also have Sprint 10 assigned and the still have Story point estimates > 0 and had them before we closed the Sprint.

[Sven Horner]

@Vasyl Krokha I also just found out that the View you requested is only availabe for company managed projects. We have a team managed project.

Found the info here:
https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-sprint-report/

[Sven Horner]

The reason for commitment being 0 seems to be that we start the Sprint with 0 issues and add them after start of the sprint. We don't understand yet, how this happens. We thought we're adding them before starting the Sprint. Will update, if we find something. But here the Burndown Chart report clearly shows this (see mouseover legend):

[Vasyl Krokha]

Hi @Sven Horner

It looks like you were able to dive into details and shed some light on the numbers you have as a result.

Regarding commitment, you are correct. If issues are added after the sprint start, they are not counted as initial commitments and are marked with *  as added after the sprint start in the sprint issue details. You can see the legend in your own screenshot.

What you could also do is check the issue change history  and find the date time when it was added to a sprint and compare with the sprint start date. Overall, next time when you start a new sprint, you will pay more attention to what is in the sprint before pushing the button :)

[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.

See also this article: https://community.atlassian.com/t5/App-Central/8-gadgets-for-a-powerful-Scrum-dashboard-in-Jira/ba-p/1683063

Hope this helps.

Danut.