Condition never being hit

Aaron Eden November 18, 2024

I have a simple condition check in an automation that gets fired any time a new story is created.  I'd like to apply Checklist Templates to my clones when they are first created.   The first condition "BSA: 1 - " gets hit and that template is applied, but none of the others ever fire when those stories are cloned.  

Thanks for your help!


Automation 
Screenshot 2024-11-18 at 3.30.08 PM.png

Screenshot 2024-11-18 at 3.36.47 PM.png

 

 

 

Stories that were cloned -- Only BSA 1 applied the template, but none of the others did :(Screenshot 2024-11-18 at 3.32.02 PM.png

1 answer

1 accepted

3 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 18, 2024

Hi @Aaron Eden 

The way your rule is structured, it stops when it hits the first failing condition.

One solution for this is to remove the Branch On Current Issue and use the if / else condition blocks for each case: https://confluence.atlassian.com/automation/jira-automation-conditions-993924794.html#Jiraautomationconditions-ifelseblockIf/Elseblock

  • trigger: issue created
  • ...
  • if / else condition:
    • test for BSA: 1 -
    • action: do something
  • else / if
    • test for BSA: 2 -
    • action do something else
  • ...

Kind regards,
Bill

Aaron Eden November 19, 2024

Weird, I never saw those if conditions in the UI.   Thanks @Bill Sheboy that did the trick and I'm up and running successfully.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer