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

Story points in the subtasks.

HI all,

We want to put story points in the subtasks.

Managing them at this level is for the following reason
we don't have a full stack developer and we need separate subtasks for Front, back, etc... as we put all subtasks inside a story we have the problem that frontend developers don't know how to estimate storypoints in a backend theme for example.
This is why we want to lower the storypoints to subtask level.

Is there a possibility to display storypoints in subtasks?
I have configured the screens and layouts and it still doesn't appear, is it possible to change this configuration?

I hope I have explained the problem correctly


2 answers

2 votes

Jira won't support you doing this directly - you are not doing Scrum, and Jira Software's Scrum boards are a Scrum tool.

The important points of Scrum for this question are:

  • A sprint item (Story) is worked on by a single, multifunctional team, one that can complete all parts of it.  You would have a front-end and a back-end developer in there who would be able to work out the estimate between them.
  • The sprint starts with a set of sprint items that the team has committed to doing during the sprint.
  • Sub-tasks are piees of their story, not sprint items in their own right.  Scrum actually has nothing to say about sub-tasks, because they're not sprint items.

Given that, you should see that putting sprint estimates (story points) are useless on sub-tasks.  They're not sprint items.  Jira goes wrong if you do it, because you shouldn't.

However, with a bit of work, you can support your way of working (of course, it's still not Scrum or Agile, because of the multi-team thing, but hey).  You need a strategy for summing estimates on to stories.  An obvious one is to just add up the points on to the parent issues, but it's actually horribly clumsy and doesn't work unless you split it into two.  A better one is to subtract from the parent rather than add (but you still need to split it up)

By "split", I mean that you need one field for "sprint estimate" (on issues only) and another for "field that we're going to calculate the sprint estimate from" (on issues and sub-tasks)

0 votes

Hi @Jaime Basco ,

JIRA natively doesn't support estimation at subtasks level. This is correct because, on Agile perspective, in a sprint you need to release something that works so you can release a story but not part of it such as a subtask.

Hope this clarify your doubt,



I know it is not quite correct, but we need this format to know the history points in the subtasks.
We need to put exactly the history points field in another subtask (in the original Jira subtask we have been able to put the field but in another subtask generated by us it is not possible).

story point subtask.JPG

We don't know why this problem occurs if the two issue types share screen scheme and issue types screen schemes


It happens because you are estimating in the wrong place.  Sprint estimates should not be put on sub-tasks, it simply does not work.


After much thought we have seen that by modifying the context of the "history points" field. We were able to add this field in the issue type screen that we needed.

Story point.JPG

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

5,067 views 18 32
Read article

Atlassian Community Events