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

Create and test Jira automation rule for closing tasks

Sierra L_

I want to make it so that once all 8 linked tasks are closed, then for the primary linked ticket: The assignee is set back to the reported. The status is set to closed. It automatically adds a comment to the original ticket

These are automation rules that I tried to accomplish this, I know I'm off track here. Any commentary is appreciated.

(Other issue types are the primary ticket, any linked item is a task issue type)

Screenshot 2025-09-16 120253.png Screenshot 2025-09-16 120322.png

Accepted answers

Bill Sheboy

Hi @Sierra L_ -- Welcome to the Atlassian Community!

Would you please clarify your scenario? Is it one of these:

GIVEN a work item which has 8 other Tasks linked to it, WHEN all 8 Tasks are closed, THEN...
GIVEN a work item with a linked Task, AND that linked Task has other linked Tasks in a chain of 8 work items, WHEN all Tasks in the chain are closed, THEN...
something else

The first one can be solved using the Related Issues Condition, although I find that one a bit unpredictable in results / behavior. Instead, try using the Lookup Work Items action with a JQL expression to find the linked Tasks for better control over the logic.

The second one cannot be easily solved with automation rules due to how branches work, although it is possible when there is a specific known number of linked work items.

Kind regards,
Bill

All comments

Corinne Guibert_lao912

I'm

When do you want the rules to be executed : when the last subtask is closed ? Or doing a hourly check is enough ?

your first automation runs when there is a transition to Open or Reopen. It should be Done (or whatever closing status your are using)

What is your selection criteria on the scheduled automation ?

Bill Sheboy

Hi @Sierra L_ -- Welcome to the Atlassian Community!

Would you please clarify your scenario? Is it one of these:

GIVEN a work item which has 8 other Tasks linked to it, WHEN all 8 Tasks are closed, THEN...
GIVEN a work item with a linked Task, AND that linked Task has other linked Tasks in a chain of 8 work items, WHEN all Tasks in the chain are closed, THEN...
something else

The second one cannot be easily solved with automation rules due to how branches work, although it is possible when there is a specific known number of linked work items.

Kind regards,
Bill

Sierra L_

Hi @Bill Sheboy

It's 1.) GIVEN a work item, which has 8 other Tasks linked to it, and WHEN all 8 Tasks are closed THEN I need that work item to be auto closed, assignee set back to reporter, add my custom comment.

Would my Lookup Work Items action with the JQL expression need to essentially say Any Issue Type that has Task Type Linked Items and ALL Linked Items are closed...THEN....

Sierra L_

What needs to happen is when the last linked item is closed, that then closes the primary ticket that all of the linked items are connected by.

The scheduled aspect was a way I thought I may have to do it, to have the system check that all the linked items are closed to then trigger the rest of what needs accomplished.

Sierra L_

Screenshot 2025-09-16 134400.png

Sierra L_

Screenshot 2025-09-16 134400.png

Bill Sheboy

Hi @Sierra L_ -- No, you could use the JQL needed to select only your specific ones. For example:

action: lookup work items, with JQL of

project = yourProject
 AND issue IN linkedIssues("{{triggerIssue.key}}")
 AND issueType = Task
 AND statusCategory != Done

smart values condition
- first value: {{lookupIssues.size|0}}
- condition: equals
- second value: 0
...continue to update the trigger work item

Please note the JQL inverts the condition to check for any not completed ones, and then tests that the count found is 0.

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