Ho to see done storypoints in the backlog view in a story is still in progress.

[johannes van staveren]

Hi there Fellow Atlassians,

A team member of mine asked the following question about Jira server totals, and I couldn't answer it nor find a answer on the forums wo I post it here.

Situation: As a scrum team member I want to have an overview of my completed story points.

As indicated by the green star, this team member has completed 0 story points in the backlog view.

However If we look at the sprint planning view we can see that she has > 0 story points in the done row.

Questions:
1: Any idea what we're doing different than the developers of Jira imagined we'd do? And how can we #align with the intended use of Jira so we get to see the actuals of the Done storypoints in Jira?

2: I understand that when a story is done you see the total of done storypoints in the green star. I want to know how I can configure Jira so that I can see the total done storypoints for sub tasks.

3: I want to know how a story can automatically inherit the total amount of story points generated by it's sub tasks. 

[Mark Segall]

Hi @johannes van staveren and welcome to the community!  The short of it is that estimations are not designed to work in this way.  Each story should be a granular enough piece of effort that serves as the lowest tier of calculating velocity. 

SubTasks are really only intended for breaking up the work on that story further such as breaking out each step of the definition of done into individualized tasks.

[Nic Brough -Adaptavist-]

The problem is a misunderstanding about what a sub-task is.  They are a part of their parent issue (story), not a separate item, and hence not a sprint item.  When you're doing a sprint, all that matters is the completion (or not) of sprint items.  Estimates on sub-tasks don't count as anything other than as part of their parent.

Now, there's nothing wrong with estimating sub-tasks, but if you do it, you need a proper summing strategy that reflects that their estimate is part of the story's estimate.

Jira has kept it simple, and not implemented any summing system other than "don't put estimates on sub-tasks".

[johannes van staveren]

Ah so now I think I get it:

So how it's intended to work in Jira is that the dev team collectively appoints story points to a user story for the total cost of time that user story takes with all development team members together to complete. 

Is that correct?

If so I got a bunch of other issues which would appear for our team.

[Nic Brough -Adaptavist-]

Yes, that's exactly what sprint estimates are for - estimating the entire story for a multi-skilled team.

[johannes van staveren]

Yeah, that's what I thought. Currently our team currently comprises of of single skilled team members. We'll get there though ;)