Scrum Report not coming up with all Story Points

Question

Hi there,

Hope someone can help me with what I am encountering. I want to export a Sprint Report. All tasks, sub tasks, bugs and stories have been allocated with a story point. I checked my board settings and all statuses have been mapped correctly. Yet, when I go to my report, I can see the story points on "stories" only and not "tasks, issues, sub tasks". How can I solve this? My team has spent some time adding story point value on each ticket type to have full visibility on story points they can do and I can't export a full report, a bit frustrating. Still looking into it, if someone has a clue on how to fix it, I will forever grateful ! Thanks in advance for your prompt feedback.

All the best,
Marion

Earl McCutcheon · Answer

Hi Marion,

This topic comes up a lot and is a bit confusing, and as covered in Estimate in story points:

Story points enable the team to estimate stories in comparison to other stories, instead of forcing them to determine the time it will take to complete each story. Velocity is then worked out based on how many points the team can complete in each sprint

Here are a few older posts on the topic going into a deeper discussion:

* https://community.atlassian.com/t5/Jira-questions/Story-Point-Estimates-in-Sub-Tasks/qaq-p/284987
* https://community.atlassian.com/t5/Jira-questions/How-to-estimate-story-points-for-sub-tasks/qaq-p/49664
* https://community.atlassian.com/t5/Jira-Software-questions/Do-SubTask-Story-Points-roll-up-to-the-Issue/qaq-p/339076
* https://community.atlassian.com/t5/Jira-Software-questions/Story-points-subtasks-gt-burndown-chart/qaq-p/178924

But ultimately the story points should not be at the Sub-Task level, and the Story Points should occur at the Story level with time estimates at the sub task level.  Stories are estimated in story points for helping the overall release planning by as a weighted item, while the sub-tasks estimates in Time Efforts (Original/Remanning estimate fields) and sprint burn down drawn to see how the sprint is progressing by the higher level weighted elements of the team not the granular time elements of the individual.

Check out this Documentation that goes into a bit more detail of the Subtask behavior on the burn-down chart vie the time tracking elements:

* Configuring estimation and tracking

Regards,
Earl

Petter Gonçalves · Answer

Hello Baillat,

By default, the context of Story points is only applicable for Epic and Story issue types, however, you mentioned that your team has allocated Story points to your Tasks, sub-tasks and bugs too.

The point is: Sometimes a different field is added/created to track Story points with the same/similar name as the default field, like Story point Estimate, Story points, etc. However, only the default Story points field appears on agile reports, so this situation can cause the confusing scenario you are facing now.

That been said, can you please confirm that you are using the correct Story Point field and that you've changed the context of the default Story Points field to also be applicable to your other issue types (Tasks, Sub-tasks, bugs)?

To check this information:

1 - Type GG and search for the Custom fields page > search for the Story Points field

2 - Check if the column Available Context(s) is configured as Global (all issues) or at least with all the issue types you would like to display it

3 - If it is not, Click on the three dots menu (...) > Configure >  Edit Configuration > select your issue types under Choose applicable issue types

4 - Make sure that the field is properly added to your project screens related to the issue types

For more information about this, you can check the documentation below:

Configuring Estimation and Tracking

Please, let me know if this information helps.