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:
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!
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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 ...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Walter, Please see below rule:
The below is correct:
What happens afterwards, Extra Sub-Tasks, "Outside"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Walter,
That Makes Perfect Sense,
Thank you very much for your assistance
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.