Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How do I configure Sub-Tasks to be included in Sprint work estimates?

Christo4 March 6, 2018

When we configure Epics, the underlying Tasks all show up as individual work estimates. However, with Stories, the Tasks created within the Story show up as Sub-Tasks and their work estimates do no carry into the Sprint total work estimate. Is this a bug? Have I missed a configuration step?

Please advise...thank you!

1 answer

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 6, 2018

No, no mistake.  Sub-tasks do not have estimates placed on them because they're irrelevant.  You commit to doing stories in Scrum, and when ending the sprint, a story is either done, or it is not. 

Christo4 March 7, 2018

I am missing something...I don't want to deal with Sub-Tasks...only Tasks.  Can I create Tasks independently and then associate them with a Story? Clearly, attempting to create a Task within a Story ends up with Sub-Task designation. Consequently, we have redefined Stories as Epochs which do contain Tasks and enable us to monitor Work Estimates and track progress. Could not get around the annoyance of the Sub-Task to Story issue. Please advise...thank you.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 7, 2018

Yes, I think you are missing something, but I think it's Jira-speak, rather than what you're doing.

Jira Software effectively has three layers:

  • Epic
  • Standard issue types (usually Stories, Bugs, Improvements, Issues, but often Tasks, Projects, Paperwork, Meetings etc)
  • Sub-tasks (Technical task, sub-task, sometimes Tasks, etc)

You'll note I've been a bit vague and flexible about the names.  This is because you can call an issue type that are Standard or sub-task types anything you want (Epics are a special case, they're actually standard issue types, but there's only one and there's extra functions for them).

I am guessing that what you call "tasks" are issue of a type called "task" and they are sub-task types. 

So, to go back to the estimation, their estimates are irrelevant because they are not what you're committing to in a sprint - it only matters when their container issue is done, and that has its own estimates.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events