Double count of estimates when using Sub Tasks?

Hey guys --

I am curious if I'm making a mistake and missing something. But I'd like to set up a way to confirm I don't "double up" on estimates for a User Story that has sub tasks.

Case is : IF I set up a Story. How can I set up validation to remove any time estimates on the story (Parent) once I set up a sub task(s) (Child Issues)?

My understanding is that the Parent story is only the sum of its parts. Is there any way to help us avoid accidental assigning of values once we set up the sub tasks?

Would this be modification in how the objects are defined?

what have others done?

2 answers

We enforce it by only having fields in one type of ticket... so for example... you can only put a time estimate in a subtask, and you can only put story points in a story (and not a subtask).

You might want to do something like that.

Yes - I am also looking at how to avoid resolving the sub tasks but keeping it's Parent story open. Also - on this point - if a sub task is CLOSED and there is time remaining. I'd like to force a validation that this should be impossible. any thoughts?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 29, 2019 in Jira Software

Transforming Jira Software projects for general project management purposes

...It's true that there are projects in Jira; but they are merely a way to cut off issues, to tell them apart from other sections of work and to apply rules that are specific to that team (the schemes)....

200 views 0 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you