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 Chart is showing incorrect commitment

Loveleen Margareth

Displays a different commitment than at the start when the sprint is complete.

The initial commitment was 135 and when everything was done in the column the total was still 135. I did the complete sprint, but when I look at the velocity chart, the commitment is actually 8. That doesn't match the complete sprint. how to change 8 to 135 to match the one in complete? and what causes this to happen?

Accepted answers

All comments

Taha El Majidi_m72glw

Hi @Loveleen Margareth

Can you check if you have a resolution on the issues you closed ?

And if you can share an example of one of the issues included in your sprint ?

Have a nice day,

Taha

Loveleen Margareth

Hi @Taha El Majidi

I don't know how to solve this problem, I already screenshot the issue and explain in more detail in the description column. please help me solve this problem. Thank you

Taha El Majidi_m72glw

Hi again,

I saw your description. To better understand the problem I just need more details about the issues you closed during the sprint. Do they have a resolution ?

Thanks

Loveleen Margareth

I completed the sprint, and the commitment should be 135 and the completed 135 on the velocity chart, but instead there are 8 and 135. See the part I circled in the screenshot above.

and look at what I screenshot below, here it counts 135 for compliance and commitment. but on the velocity chart the numbers are different

Marc -Devoteam-

Hi @Loveleen Margareth

Has there been a change on the projects Workflow and/or Sprint Board?

If there was and a previously used status was removed from the flow and the board, this can happen.

Are you also able to share the sprint report?

Loveleen Margareth

sure @Marc -Devoteam-

here it is

Danut M _StonikByte_

Hi @Loveleen Margareth,

Please try the following:

Check if the issues were added in sprint after sprint start date. This can be checked in the issue history.
Check if the issues were added in sprint with no estimate, and estimation was added after sprint start date. This can be checked in the issue history.
Try also the velocity chart offered by our Great Gadgets app. It uses a different calculation method than Jira reports and might display correct data.

Team Velocity Gadget

This gadget offers also a data tab, with details about every issue in the sprint.

The Data tab showing sprint details

I hope this helps.

Thank you,

Danut Manda

Marc -Devoteam-

Hi @Loveleen Margareth ,

I see why the initial commitment was 8, this was the only issue in the sprint on starting.

All issues have been added after the sprint start.

If they would have been in the sprint from the start your burn-up report would show the start to work scope at 135 not at 8.

You see the red line moving to 135 after the start.

Taha El Majidi_m72glw

Dear @Loveleen Margareth ,

The "None+1" is a display introduced by Atlassian sometime now. Sorry I was not aware of that. But this display is not the source of your problem.

What @Marc -Devoteam- explained is the problem here with you report, Atlassian explain the following :

Commitment: The gray bar for each sprint shows the total estimate of all issues in the sprint when it begins. After the sprint has started, any stories added to the sprint, or any changes made to estimates, will not be included in this total.
Completed: The green bar in each sprint shows the total completed estimates when the sprint ends. Any scope changes made after the sprint started are included in this total.

You can find more details about velocity charts here.

I don't think a solution for this sprint is possible, you can always check your burndown chart to explain what happened in this sprint.

Thanks,

Loveleen Margareth

Dear @Marc Koppelaar okay, so how can I solved and change it from 8 to 135 in velocity report?

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-service-management-cloud

jira-service-management