We have a company managed project. I have set board settings>estimation to story points. But at the end of a Sprint, when its closed, there is aren't metrics displayed.
Hello @Travis Scudder
Welcome to the Atlassian community.
Are you viewing a Velocity report associated with board for that gets issues for only a single project, or for multiple projects?
Do the issues in the board appear in other boards?
Are you assigning values to the Story Points field in the work items in your Space that are getting added to the Sprints?
The Committed value reflects story points assigned to standard work item types (not Epics or Subtasks) that are in the sprint when you click the Start Sprint button. It appears that there were either no issues in the sprints at those times, or they had not Story Points values.
The Completed value reflects story points assigned to the standard work item types in the sprint and in the column farthest to the right when you click the Complete Sprint button. Are there such issues in the right most column of your board when you are completing your sprints? It appears that there were for at least the Sustained Eng sprint.
Have you made changes to the mapping of statuses to columns in your board?
Have you made changes to the Filter used by your board? The report will show data only for the issues that match the Filter for the board you are currently viewing.
Hi @Travis Scudder,
Welcome to the Atlassian Community!
A common reason for seeing 0 SPs under Completed is that the board’s last column (far right) does not map the Done statuses. However, the fact that the report shows Completed for a sprint but 0 for Committed suggests a different issue.
One possibility is that issues were added or dragged into the sprint after the sprint planned start date. Did you also check the other reports for those sprints, such as the Sprint Report or Burndown Report? Do they show same wrong data? Check also the history of the issues, to see if they were added in sprint before the sprint start date.
If the issues look correct, you may contact Atlassian Support for assistance.
If you’d rather avoid struggling with these Jira reports, another option would be to try an app (plugin) from the Atlassian Marketplace.
If you'd like to try an app, our Great Gadgets app includes a Team Velocity gadget that works similarly to Jira’s report, but offers more advanced functionality, additional metrics, and a high level of customization. It may be worth trying to see whether the same issue occurs there as well.
Hope this helps.
Danut
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you're on Jira Service Management, the native email channel handles this easily. For standard Jira Software, you'll need to configure an incoming mail handler.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Travis Scudder
Welcome to the Atlassian community.
Your answer talks about email handling, not the question concerns velocity reports. Perhaps you meant to add your answer to a different question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community!
As for all the points mentioned by @Trudy Claspill , you can also try a quickdiagnostic:
Pull up the Sprint Report (not the Velocity chart) for the same sprint .
Does it show your issues and their story points in the "completed" section?
If it does, the disconnect is likely the board filter or column mapping. If the Sprint Report is also blank, the story point field itself might not be wired up properly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.