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 and Sprint report error ?

Saloua_Toumi

Hello everyone,

I've added estimated stories to sprint before starting the sprint. My sprint report shows that I completed 70 story points with one Issue removed from sprint (5 SP).

My burndown chart shows the same, started with (75 SP), one issue removed, completed 70 SP.

The velocity chart on the one hand tells me that I've committed to 104 SP! and completed 70. I really don't understand where does 104 come from.

There was only one story (5SP) removed from sprint after the start of the sprint.

Could it be possible that it counted stories added and removed from sprint BEFORE starting the sprint ??

Accepted answers

Saloua_Toumi

Hello guys,

Very sorry for the delayed response, I couldn't share the screenshots with you unfortunately.

However, I think I figured it out : there were some issues with status CANCELED that were still in the backlog and moved from sprint to sprint.

I couldn't see these canceled issues in the sprint report, because the status was not mapped in the board.

I hope this would help someone in the future. Thank you all for your time and patience.

All comments

unknown

Hi @Saloua_Toumi,

quick question; did you remove any standard issue types such as Stories from the sprint after starting it?

thanks

Saloua_Toumi

Hello,

Yes, there is one story ( 5SP) removed from sprint after starting it.

unknown

Hi @Saloua_Toumi,

Apologies for the late reply, were any sub-tasks converted to standard issue types and vice versa during the sprint?

Thanks

Saloua_Toumi

Hello @[deleted]

No such thing is defined in Jira showing that sub-tasks were converted and vice versa.

Saloua_Toumi

Hello @[deleted]

Sorry for the late response, I've looked into Issue History, no stories or sub-tasks were converted.

We haven't changed our behavior from last Sprints, but for this one, we really don't how that might have happened.

Can you give me some exemple cases why such thing can happen in Jira please?

Thank you for your time and patience.

Scott Theus

Hi @Saloua_Toumi,

Do you know if there were any stories in the sprint that were moved to the "done" status multiple times within the sprint? (For example, a story is completed and moved to "done" only to later discover something incomplete; it is then moved back to "in process,' completed, and moved back to "done.")

-Scott

Jack Brickey

@Saloua_Toumi, It might help if you could provide screenshots of sprint burndown report. Not sure that will clear the fog but we will need something to work with here.

Tarun Sapra

Just to add to what Jack already shared , @Saloua_Toumi can you share screenshots of the 3 reports

Sprint report

Burndown chart

Velocity Chart

Saloua_Toumi

Hello guys,

Very sorry for the delayed response, I couldn't share the screenshots with you unfortunately.

However, I think I figured it out : there were some issues with status CANCELED that were still in the backlog and moved from sprint to sprint.

I couldn't see these canceled issues in the sprint report, because the status was not mapped in the board.

I hope this would help someone in the future. Thank you all for your time and patience.

unknown

Hi @Saloua_Toumi,

Great news that you got it sorted.

Have a great day

Scott Theus

Good news, thanks for sharing the answer!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

velocity

sprint

report