Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Summarizing story points from sub-tasks in parent task

We are currently estimating our work on a sub-task level by using story points. The user story (or other issue type) has no story points if it has sub-tasks. If there are no sub-tasks, then we add the user stories to the story itself.

We split user stories into front- and backend sub-tasks. The assignee of the sub-task then estimates during sprint planning and the user story is added as a whole to the sprint. This increases the sprint scope by the sum of both sub-tasks.

Is it possible to display the sum of all story points of sub-tasks and display it on the sprint board and backlog?

Also, it seems that the Epic report only works with story points on the user story level and not sub-task level. Stories that have sub-tasks with story points are shown as unestimated. Any idea how to best report on Epic progress with the described approach? How are you storing the estimated story points when working with sub-tasks?

5 answers

3 accepted

7 votes
Answer accepted

Hi Marco, 

This comes up quite a bit, but to summarize story point estimation is expected at the story level and time estimates at the sub-task level. The native sum up options will sum the time tracking of the sub-task to the story and to do this set the Remaining estimate and time spent value as covered here:

Also there is some more detail on this in "Estimating an issue" towards the bottom in an expandable section titled "Why not estimate on subtasks and roll that up for Velocity and Commitment?"

Additionally, the following posts discuss story point summation to the parent in even more detail:

So its not expected behavior and you would need to look into an add-ons to get this to occur, and I know there are some examples of doing this in ScriptRunner such as the following Post which gives an example on how to do this via a scripted field, however Cloud does not support the functions that allow Script Runner to add field types to it as it does on Server, and I am not aware of an add-on in cloud that does this:


Hi @Sarvesh Mathur ,

Good call out, and thanks for posting the info in this thread. 

Now that Automation for Jira is integrated with Jira Cloud natively, the solution noted in your link will work out as a great alternative.


Like Tanja likes this

Do you incorporate points for the QA effort?  and if so, where do you incorporate those?  Maybe in the main story I would assume.

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you