Making Subtasks dependent on one another

[Julianne Slagle]

I have an epic with multiple stories underneath it and within each story I have a set of subtasks. I need the subtasks within these stories to be dependent on each other.

EPIC-Stories-Subtasks

When subtask is started on, and in progress, I need this to reflect and be dependent on the start and due dates.

So, if any story/subtasks are not complete then the project will not be able to be implemented. 

[Laurie Sciutti]

Hi @Julianne Slagle and welcome to the Community! 

1) What about automation to create the dependent sub-tasks on transition (or closure) of the previous sub-task rather than creating all sub-tasks at once?  

2) you can use Branching conditions in your automation to update the parent start / due dates

3) Add a workflow condition on resolution transition that checks sub-task closure or a workflow validation to check for issue links closure

[Julianne Slagle]

Thank you @Laurie Sciutti need to figure out how to do all the above but thank you for suggestions :)

[Laurie Sciutti]

Hi @Julianne Slagle ~ here's a start!  You can add another action under the For Parent section shown below to set Start, Due Dates and anything else on the related Parent....

[Julianne Slagle]

Thank you! I already have all the subtasks created, so will i just need to type the name of my subtasks in so it automatically takes those into the workflow/automation?

[Laurie Sciutti]

Hi @Julianne Slagle ~ I'm not sure I understand your last question?  The example rule I provided shows how to automatically generate additional sub-tasks on resolution of another one with the same parent.  If you want to replicate that, it would be for new issues created where those dependent sub-tasks exist.  If you want to do that, then at minimum you will need to set the Summary field for those sub-tasks (as that is a required field) but you can certainly add additional fields to auto-populate in your rule.

If you're asking how to address the dependency for existing sub-tasks, then this rule won't work ~ you'd need to create a different rule or workflow condition, depending on how you want it to process.  Maybe you don't want those dependent sub-tasks to be closed until the precursor is closed.  In that example, you may want a workflow condition or a validation.  A rule may work, but I'd need to know how you want to process those dependencies for existing sub-tasks.  Do they have a specific component / label you can check in your Rule?  Or a specific Summary prefix?