nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to automate parent transition when a number of sub-tasks is closed

George Stamos

Hello everyone,

First of all I would like to know if what I'm trying to do is feasible with Jira project automation.

Use case: Having a story with a number of sub-tasks (i.e. child issues) I would like to automate the transition of the Story (i.e. parent issue) when all sub-tasks with Design component for example are move to Done i.e. when all orange sub-tasks (or last orange) are moved to Done. Is this possible? If yes, how can I manage this?

So far I know how to move my story for example to Design as soon as the first sub-task moves to In Progress. I also know how to move my story when all sub-tasks moved to Done. What I cannot figure out is how to transition my story when a sub-set of my sub-tasks is moved to Done.

Thank you in advance,

George

Accepted answers

All comments

Stefan Salzl

Hi @George Stamos ,

Do the subtasks have the field "Component" filled with component "Design"? Or is color the only way the are detected as Design issues?

Best
Stefan

Stefan Salzl

In case there is a component "Design" in the SubTasks the following rule should do the work as expected:

Looking forward to your feedback.

Best
Stefan

George Stamos

Color coding was for the sketch . It is component as you thought so. I forgot to mention I'm on a data center not cloud though .

I'll give it a try to see if i understood correct and let you know.

Thank you for sharing Stefan Salzl

Stefan Salzl

hi @George Stamos

thanks for the information. That‘s a game changer as the lookupIssue action is not available for data center 🙈

need to rethink the solution 🤔

Best
Stefan

Sachin Dhamale_o1c5zi

@George Stamos ,

Can you try this automation rule

automation transition.png

Accept the answer if it helps

George Stamos

Hello @Sachin Dhamale ,

Thank you for sharing!

Unfortunately this doesn't fall to the case I'm after.

It doesn't work for me

Best regards,

George

Bill Sheboy

Hi @George Stamos

Would you please clarify something about your use case? That may help the community to offer you suggestions to help.

You describe a need to move the parent story to "done" when a subset of the child subtasks (e.g. the orange ones in your picture) are all "done".

What work do the "blue" subtasks represent that they do not also need to complete for the story to be considered complete? For example, are they optional and so are abandoned when the "orange" ones are all completed?

Kind regards,
Bill

George Stamos

Hello @Bill Sheboy ,

As shown in the picture, I want to move my story I.e. parent to the next flow step when a subset of my sub-tasks is moved to done.

Bill Sheboy

Thanks and I understood that from your picture.

I was asking: why would the other subtasks not need to also finish before marking the story as "done"?

Is your intention work would continue on the other subtasks even though the story is marked as "done"? If so, measuring what you describe as cycle time would be inaccurate as it misses some of the working time.

George Stamos

Moving design sub-tasks to done would mean according to our policy for example that design phase is concluded meaning our story need to move to the next flow step. Same if blue ones move to done then another flow step will follow for the story etc.

To be honest I never mentioned I want to move the story to done. This will happen only if all sub-tasks are moved to done.

Hence there is metrics as you assume correct that Measure lead time as well from To do to done.

Nevertheless this is not what is this thread is about 🙂, thank you for asking

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

atl-gruland

automation