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

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

Melanie.Johnson

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?

Accepted answers

All comments

Trudy P Claspill

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

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

Trudy P Claspill

Please show your entire rule.

Melanie.Johnson

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

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud