I have an automation with the following goal/setup:
1. When we indicate "Yes" on a Billable Field (custom field), for any ticket, a new ticket is created.
2. The new ticket is linked to the trigger ticket
3. On the new ticket, fields are copied from the trigger ticket
4. One of those fields is the second trigger "Client". IF = "Non Client" - assign a particular person (on the new, secondary ticket) and move the workflow.
5. If the trigger is anything OTHER than non-client, then it assigns someone else, and moves to a different stage of the workflow.
My results have been mixed, but typically its creating the ticket fine, linking the issue fine, and then it tends to follow the second branch, not the first, regardless of the parameters I set.
Said another way: Looking at the automation screenshots I'm only getting one result, it doesn't seem to recognize the secondary triggers and apply the correct path.
Hello @Jared G
Branches are not an either/or construct. All branches in a rule will execute.
You can put a condition in the branch to determine if it should continue executing, if the steps in the branch apply only under specific circumstances. You have such a condition in your first branch, but not in your second branch. So your second branch will always execute all its steps. You need to add a condition to it if you want it to execute only under specific conditions.
Additionally be advised that branches execute in parallel, not sequentially. Refer to
Because of that parallel execution for branches you might want to instead separate those steps out to another rule trigger by Issue Created, where you add a condition to check if the newly created issue meets conditions that tell you it was created through the first rule. In that second branch you could then use and IF-ELSE construct to say:
If "Client" = "Non-client"
--- execute some steps
ELSE
--- execute other steps
https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/#If-else-block
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.