Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Incorrect sprint story points summary

pawel_dudziak
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 27, 2023

Hello everyone,

we've just started to estimate our tasks in Jira. During our first spring I'd say, everything was fine with SP summary (on backlog tab, upper right corner) but with our 2nd sprint, everything is incorrect. We've estimated over 100sp and we can see only 58 story points.
Have you got any idea, what happened?

2 answers

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 5, 2023

Sub-tasks won't appear on a backlog, they're functionally useless in backlogs because you don't put sprint estimates on them (they're a part of a sprint item) and you can't rank them outside their parent.

If you are putting sprint estimates on sub-tasks, that would explain the numbers going wrong - Jira will be ignoring the estimates on them.

If you do want to put estimates on sub-tasks, then yes, you will need to automate something to make them work with your sprints, but one note of caution - use two fields. 

If, for example, you are using "Story Points" as your sprint estimate, then have that field on your standard level issues, but not sub-tasks.  Add a new field like "Sub Story Points" and automate calculating the parent Story Points from it.

0 votes
Dave Mathijs
Community Champion
June 27, 2023

Hello @pawel_dudziak welcome to the Atlassian Community!

Can you show us where you see those 58 story points? Do you have a screenshot?

pawel_dudziak
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 27, 2023

hello,

after intensive research I think I've figured this out. So, we don't have sub-tasks (like BE, FE, test sets etc) on our backlog and we haven't mapped child-issues to parent SP summary, so backlog only shows us narrow piece of our SP - only tasks not linked with any other issues. I'll try to map all child issues with parents and make some automation and let you all know if it works. ;)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events