Automation

Andile Luvuno
Contributor
January 18, 2025

Hi.

I would like, for every Issue created, 10 Sub-Tasks must be created inside each Issue/Task

How can I achieve that using Automation?

1 answer

1 accepted

8 votes
Answer accepted
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 18, 2025

Hi @Andile Luvuno,

For a scenario like this, I would assume your sub-tasks are fixed / default sub-tasks. Quite simply, set up your automation rule like this:

Screenshot 2025-01-18 at 14.12.10.png

The condition I added in the second step is a way to control that subtasks only get created when my created issue meets certain criteria (in my example, if it has the label Jira. But, obviously, consider what makes sense for your use case).

Every Create Sub-Task action allows you to set specific fields. In my example, I am creating 4, but you can add more of course.

Hope this helps! 

Andile Luvuno
Contributor
January 18, 2025

Hi Walter,

Thank you for the response, 

This works, however, i have a slight issue, when the rule ran, it created the Sub-Tasks inside Each created Task and then proceeds to create the same Sub-Tasks Outside as New "Sub-Tasks"

How Can I prevent that from happening, so it only creates the Sub-Tasks inside the intended Tasks?

Thank you.

Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 18, 2025

Hi @Andile Luvuno,

sub-tasks can't be created without a parent, so you honestly got me confused there about this statement:

when the rule ran, it created the Sub-Tasks inside Each created Task and then proceeds to create the same Sub-Tasks Outside as New "Sub-Tasks"

Can you share (a) screenshot(s) of your full automation rule and evidence of what goes wrong, so I can understand what you mean ...

 

Andile Luvuno
Contributor
January 18, 2025

Hi Walter, Please see below rule:

Rule2.png

The below is correct:
What is required.png

What happens afterwards, Extra Sub-Tasks, "Outside"
Que Outside.png

Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 18, 2025

Those are not extra sub-tasks, @Andile Luvuno. They are the same sub-tasks as in your second screenshot (you can see that by their issue key).

The last screenshot is a view from - what I think to derive from the visible part of your screen - a JSM queue. That is just a view that just lists all your issues, but is not capable of displaying issues in a hierarchy. If you want to display only your main tasks in that queue, you'll need to update the filter that displays the issues there. Near the top right of your screen, there is a button (if you have sufficient permissions) ... that allows you to edit the queue. If you update the filter there to add something like this:

Issuetype in standardIssueTypes() AND [whatever is already there as your
current queue filter]

the subtasks will no longer show there. But rest assured, they are not duplicates and they are linked to your parent issue, as you demonstrated with your second screenshot.

Andile Luvuno
Contributor
January 18, 2025

Hi Walter,

That Makes Perfect Sense, 

Thank you very much for your assistance

 

Suggest an answer

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

Atlassian Community Events