Is it possible to see the total workload per user (subtasks) in the Sprint planning summary?

[Leonard Stirbu]

Hello everyone,

We've been using JIRA for some years now but we've hit a feature wall that we couldn't resolve so far. I'll explain our process in hopes that someone might have a solution.

First of all, we're using strictly time estimation for our work. Before a new sprint starts the Product Owner creates stories along with their specifications. In the grooming session for said sprint, the developers discuss the stories and then create sub-tasks for each one depending on their technical needs, while also estimating the time it would take for each sub task to be completed. The time total from the sub-tasks is added to the parent Story.

Most of the time, multiple developers will work on the same story, and each one will have a number of estimated sub-tasks in that story.

Now, the above generates some issues for us in the planning session. When adding Stories to a new sprint, in the estimation summary per assignee we only see the total time estimated for stories, and not for sub-tasks. This leads to situations where a developer will look like he's overbooked if he's responsible for or more stories, even though, in reality, that time is split between 3 or 4 developers, through sub-tasks.

Is there anyway we can see the estimated time per assignee for sub-tasks? It's becoming increasingly difficult for us to plan sprints, since we have to do the calculations by hand (also the JIRA reports become useless for us).

Screenshot with a wildly inaccurate worklog: 

[Petter Gonçalves]

Hello Leonard,

This behavior was already reported to our development team before. Although this is an intended behavior, there are some possible workarounds and options that you can use to estimate your issues as you need.

You can check some of these options in the feature request below. Also, please feel free to vote and watch this feature request so you can be aware of any updates:

- Would like to see sub-tasks estimation in the main task on the Plan Mode of the Rapid Board

My personal recommendation is that you can use the relation Epics > Stories instead of Stories > Sub-tasks for your estimations.