Multiple subtask creation stops after first block
I'm trying to set up a daily automation that creates subtasks under multiple parent issues, but the rule stops after processing the first parent task. Here's what I'm trying to achieve:
Current Setup (not working properly):
When: Scheduled daily at 9:00 AM If: Issue key = FIB0PT-94 Then: Create 2 subtasks If: Issue key = FIB0PT-96 Then: Create 2 subtasks
3 answers
Hello @Mohammed_Zeyad
When you use a simple IF condition the rule will stop running with the first IF condition that does not pass.
If the issue key matches Condition 1 then the Create components immediately following 1 will be executed. When the IF condition at Condition 2 is evaluated, it will fail because the issue key does not match, and the current loop of the Scheduled rule will stop running.
If the issue key does not match Condition 1 then the current loop of the Scheduled rule will stop running immediately.
You will never get a loop of the Scheduled rule that will match conditions 2..n because the rule cannot match both Condition 1 and any subsequent condition.
How do you determine the issues under which subtasks need to be created? Is it always the same set of issues that are getting subtasks? Do you specify the issues using the Execute JQL option in the Scheduled trigger?
Are you creating identical subtasks under every issue, or do the subtasks differ depending on the parent issue?
If the subtasks are identical for every issue, and you are specifying the issues using the Execute JQL option in the trigger issue, then you don't need the IF conditions at all. Following the Scheduled trigger simply add the components to create two Subtasks. Those same two Subtasks would be created for each issue retrieved by the JQL of the Scheduled trigger.
If the Subtasks need to be different for each parent then you need to use the IF/ELSE condition.
With If/Else the rule checks if the first condition passes. If it does then it executes the components directly below that condition. The rule then skips all the Else If conditions and proceeds with the steps that follow that block.
If the first condition doesn't pass, then the rule check the second condition (the Else If). If that condition passes, then the steps following it are executed, and the rest of the Else If conditions are skipped, and the rule proceeds with the steps that follow after the If/Else block.
Hello @Mohammed_Zeyad
In your current rule you must select the issues to operate against. How are you doing that? Based on what I see you must be using a JQL in the Scheduled trigger. Please share the details of the trigger and the details of the JQL.
When a JQL is used in the Scheduled trigger the actions in the rule will be executed against each of the retrieved issues from the JQL. In that case the If/Else option will absolutely work as I described.
This is just one way to accomplish the requirement and will require maintaining a lot of components in your rule.
There are other ways to accomplish this with Automation. For example
- In each of the 9 tasks create a copy of each of the subtasks that needs to be created daily and add a label to it like "subtask-template"
- Create a rule with a Scheduled trigger and a JQL to select the 9 tasks.
- Add a Branch - For Each Sub-task
-- Condition: If Labels contains-any-of subtask-template
-- Clone Issue
Hey @Mohammed_ZeyadIf you have 9 tasks with distinct recurring subtasks that need to be created daily, I think Templating.app could also be a good alternative for you.
- You can easily create issue templates for hierarchies epic, issue, subtask
- These templates also work with automation support
You can find us at the Atlassian Marketplace ➡️ https://marketplace.atlassian.com/apps/1224664
This is how this might look like:
Hi @Mohammed_Zeyad
Thanks for the answer.
Please try this solution.The second image is the For Each branch comparison, what to write there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.