Can you create a subtask that is dependent on another subtask being closed?

Melanie.Johnson
Contributor
February 20, 2025

We have an automation rule built when onboarding an employee several subtasks are created. We are looking to having another subtask created once a specific subtask is marked complete.

Example:

10 different subtasks are created once the onboarding issue is completed. 

When the Account is created (one of the 10 subtasks) subtask is marked complete, we would like a new subtask to enter the users into the system to be created.

Has anyone done this?

 

1 answer

1 vote
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 20, 2025

Hello @Melanie.Johnson 

That would be a fairly straight forward automation.

TRIGGER: Issue transitioned
  Destination status: Done

CONDITION: issue Fields Condition
  Issue type equals Subtask

CONDITION:
  Here you would define another condition that you can use to determine it was the Account Created subtasks that was transitioned

ACTION: Create Subtask

Melanie.Johnson
Contributor
February 20, 2025

Thank you!  I am assuming that I would need to place the name of the Issue in the Workflow so that it knows which subtask needs to be closed.  Below is the rule of the subtask which needs to be closed in order for the new subtask to open. All other subtasks do not need to be closed in order for the new subtask to be created.

I am unsure how I can pull the name of the subtask below onto the rule

Capture.JPG

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 20, 2025

Please show your entire rule. 

Melanie.Johnson
Contributor
February 20, 2025

Rule is below. The circle yellow is the subtask which needs to be closed in order for the new subtask to open 

 

Capture.JPGCapture2.JPG

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 20, 2025

Perhaps I have misunderstood your requirement.

Do you want to trigger creation of the dependent task on the closure of the identified task?

Or is the dependent task getting created within the existing automation rule?

If the dependent task is already getting created, then:

Is your requirement to prevent it from being transition to "in progress" unless the predecessor task has been closed?

Or is your requirement to automatically transition it to "in progress" when the predecessor task has been closed?

Melanie.Johnson
Contributor
February 20, 2025

Yes, I would like to trigger the creation of the dependent task on the closure of the identified task. My thinking is that I would create a whole new rule but was not sure if it was possible so do not have a new rule in place.

I would want the new subtask to be created and assigned to the appropriate person (I know that part of the rule LOL) and it would be waiting for support. The assignee would then begin the status changes.

 

I apologize if I confused you but I greatly appreciate your input.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 20, 2025

Thanks for the clarification.

Then, looking at the example rule I suggested:

TRIGGER: Issue transitioned
  Destination status: Done

CONDITION #1: issue Fields Condition
  Issue type equals Subtask

CONDITION #2:
  Here you would define another condition that you can use to determine it was the Account Created subtasks that was transitioned

ACTION: Create Subtask

In Condition #2 you would need to add the check for that would identify the predecessor task. If the Summary of that task is a unique string the you could use another Issue Fields Condition

Summary equals type in the Summary from the predecessor task

 

Like Bill Sheboy likes this
Bill Sheboy
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.
February 20, 2025

Hi @Melanie.Johnson 

Yes, and...to Trudy's suggestion, as she is suggesting adding a second rule to create the additional subtask, not to add to your first rule. 

I just wanted to confirm you understood that.  Thanks!

Kind regards,
Bill

Like Melanie.Johnson likes this
Melanie.Johnson
Contributor
February 21, 2025

Thank you all!  I will try this and let you know the results.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events