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; } } }

Automation that triggers an action in the "next" sub-task in a list when the prior is closed.

Ben Weisman

Hello,

I am working in a Team Managed Project within JWM. I am trying to create an automation that does the following:

When Sub-task A is closed, an email is sent to the assignee of Sub-task B.

When Sub-task B is closed, an email is sent to the assignee of Sub-Task C.

And so on...

Is this possible?

Accepted answers

All comments

Jack Brickey

Hi Ben,

I don't believe there's any way to determined/define "next". I wonder if you could create the next subtask once the first one is complete rather than creating them all ahead of time? Could be problematic if the assignee is dynamic.

Ben Weisman

Thanks @Jack Brickey . The assignee's are assigned ahead of time and could vary. Any other possible workarounds?

Jack Brickey

pondering...

What about this idea...

Using either a custom field or maybe labels, you would flag each sub-task chronologically, ST1, ST2, ST3..., at the time they are created. Your automation rule could then assess which sub task just triggers the rule and using that information could then action on the next chronological sub-task. Further, if you were to use a customer number to field you could use smart values to increment it in your assessment/action.

Complex, yes, but doable.

Ben Weisman

@Jack Brickey But every task would have to have a unique identifier manually entered, yea?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management