Workload calculation for sprint does not reflect subtask assignees

[Alexander Christian]

Hi there,

I have a problem with the general understanding of how stories are broken down into sub-tasks and and how the asignee is handled...

my scenario/my understanding:

I have a story. The story is assigned to me. It's my responsibility to track the content and the progress. etc. The story itself has no estimation so far, because the work in done in the subtasks.

I have created a sub-task for this story. I cannot work on this, it's a job for my colleague, because he is the expert in this area for this subtask. So the subtask is assigned to him and the subtask is estimated with 1hr.

This sreenshot shows this example scenario:

So far, so good.

But when I want to plan the print, I need to know who has how much planned effort. But look what jira tells me when i click the three dots near 

The effort is on the sub-task of the story for my colleague... But this is not shown here. It's related to me, obviously because it's my story... But part of the story needs to be done by someone else..

My workaround would be:

A story has one assignee and it needs to be ensured that only this assignee is assigned to _all_ subtaskks to be able to correctly track/show the required effort on sprint level.

But this would make working on a story more complex, because there then can be only one person for a story for all the required work. But Jira allows different assignees on sub-tasks... That's confusing...

I want to go "the default way" and not introcude a custom workflow or rule. So how is it really meant in jira to plan and break down a story?!

Could you please shed some light on this for best-practice?


[update]
I tried to dig deeper into this problem. I found this blog post:
https://www.atlassian.com/blog/jira-software/break-decomposing-user-stories-jira

It says: "And then there were sub-tasks. Some teams use them to enumerate the discrete steps involved in completing an issue. Other teams like them because, in cases where multiple people are required to complete the issue, five sub-tasks can be assigned to five different people instead of having to change the assignee."

So, from this point of view, my process is okay. But the workload calculation is not correct. Is this really a bug? Or can someone else explain how should I easily see/know how much effort for each individual developer is planned for this sprint, so that I know about adding/removing items from backlog is required. 

[update]
Sadly, I found this: https://jira.atlassian.com/browse/JSWCLOUD-15991

Reported in 2017 and still not solved, even not assigned to someone :-( 

[Alexander Christian]

This is so obvious... Why doesn't anyone know what the preferred way is?