Wow this issue is created in 2014, now we are in 2022 and still nothing, WOW. is it not clear in the attachment where the problem is? LOOK at the 1st attachment and you can see that poor "Max Taylor" has 0 story points, even though he might have 100 subtasks assigned to him, even though he still has 0 story points because the PO or whoever has the main story assigned to him, so later in the reports we can easily see that max taylor has not been working and he has been doing nothing the whole sprint, we should just kick him, also when planning the sprint we can not see how much workload max tyalor has

+1

This is absolutely crucial for us. Subtasks are their own entity when estimating an individual's capacity per sprint and like the others above, our story belongs to the Product Owner and the subtasks are the steps to get the story completed and they belong to the developers, QA team, database team, etc. where they own their own points and hours.

If you could define how you want story points in subtasks to be used, that would be best. Because i know some people add all the subtask points and put them in as the points for the story, but we do not. The points for the story are individual to the PO and the subtasks are individual to the assignees of them. I understand why others may do it a different way, but we are being forced to because they also want individual's story points in other reports outside of planning for the team. (Not my choice,  hence the "forced" part of my answer)

My issue is with the inconsistency of the interface of the backlog

if you estimate individual subtasks, they get added up (on top of the story estimate) in the in the workload at the top of each sprints but the number next to the story is unaffected and the estimate in the version detail does not include the subtasks estimates. You either add subtasks or you don't but you can't blame Agile methodology for having an interface that is not unified in it's behavior

currently I can't get the team to use Versions because it's a broken feature since we started to estimate subtasks

+1 Very looking forward to this feature! Currently, we are using the Workload Pie Chart when planning a sprint, because it's the only thing that shows the workload correctly. It would be so much better if the Sprint Workload also showed the correct data.

+1
Maybe not needed or comply with Scrum Agile principles,
but when Jira is used, for example, manage Art Outsourcing production, accurate workload assessment by Assignee for next sprint is key step before start it.
Current workaround is to proceed Excel Export and use Pivot table which is obviously cumbersome in team meeting context.
Actually this ticket should not be a "suggestion", it should be upgraded to Bug or Improvement request (since the UI code of Workload by Assignee is already done)
Thanks!
J.

Totally agree

We also create sub-tasks during sprint planing for different people involved in implementing a story (development, integration, review, testing). Could we please have the subtask estimate included in the workload by assignee or is is imporsible to plan sprints!!!

I agree, this is necessary. Seems like subtasks sum are not correctly handled everywhere in the UI, sadly

We create sub-tasks during sprint planing for different people involved in implementing a story (development, integration, review, testing). Could we please have the subtask estimate included in the workload by assignee!

Furthermore, we use the "original estimate" method (not story points!) to estimate our work. And as we are not estimating the story itself, but accumulating the sub-task estimates, the story shows up as "not estimated" in the backlog (which is completely wrong and does not show the actual workload). As long as we do not have sub-tasks included in a separate column, how about at least accumulating the sub-task estimates on the story?

Thank you!

I agree with Malin, provided that you make the "Hours" column "Remaining Hours".

Maybe something like this? I think that would be great!