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

Issues in sprint does not appear as completd and story points are not reflected in velocity chart

Krithica Gowri Shankar

Hi,

I have 10 issues in sprint of which 5 are in DONE status and the other 5 are marked as Done and then mapped to closed status.

Board column has Done as last status.

Now when i complete sprint, the issues that are in Done status alone is counted as completed and remaining are shown under issues removed from sprint and incomplete issues column. The velocity chart shows only the story points of these completed issues. When the issue is moved to Done now the velocity chart does not add up the completed story points.

Is this the expected behavior?

Few issues are shown under issues removed from sprint column and few under incomplete issues column? Why is it so?

Kindly help.

Thanks,

Krithica

Accepted answers

Andreas_obxgjv

The velocity is calculated by the scrum board. It basically counts all issues moved to the very right column of the board as "done within the sprint". So your board configuration has to map all the status that you and your team consider as "done" in this column (and only there).

Can you describe in more detail, what you mean by

are marked as Done

and how does this differ from being in DONE status.

Each issue has a field that holds the sprint information. If you modify this field in any way during the period of the sprint so that the current sprint of your board isn't included in that field anymore, the board will show them as removed from sprint.

All comments

Andreas_obxgjv

Can you describe in more detail, what you mean by

are marked as Done

and how does this differ from being in DONE status.

Krithica Gowri Shankar

Thank you. There are 2 status Done and closed in the workflow.

I moved the issues to Done first and then close it. These issues are completed anyways.

But the board config has Done in the right most column and not closed.

So all these issues which are in closed status are displaying under incomplete ones.

Why is it happening so?

Also do you say that if the issue has been mapped to more than one sprint it will be displayed under removed from sprint column?

one more question, 1 issue is in sprint 1 and sprint 2 now. But i could see it only under sprint 1 removed column and not in sprint 2 or in backlog also. I dont understand where the issue will be now? Its still not completed.

Krithica Gowri Shankar

And can we add story points to the velocity chart once after sprint is closed ? Like i complete issues after the sprint completes. Will this be counted in velocity chart?

Andreas_obxgjv

Why is it happening so?

Because "Closed" is not mapped to the very last column of the board. You have to map both status "Closed" and "Done" in the last column of the board, if you want them to be accounted in the velocity chart of the board.

Also do you say that if the issue has been mapped to more than one sprint it will be displayed under removed from sprint column?

No. If the sprint field of an issue was modified during the duration of a sprint and now doesn't include that sprint anymore, it will be shown as removed from sprint.

one more question, 1 issue is in sprint 1 and sprint 2 now. But i could see it only under sprint 1 removed column and not in sprint 2 or in backlog also. I dont understand where the issue will be now? Its still not completed.

What's the current status and resolution of that issue?

And can we add story points to the velocity chart once after sprint is closed ? Like i complete issues after the sprint completes. Will this be counted in velocity chart?

You can always modify story points of an issue but keep in mind that if you do so after the sprint is closed, the calculation of the velocity will be correlated with the time span of the sprint. So this will be shown as a scope change and not as the initial values.