In a for each branch, how do I use IF/ELSE

[Manav Shah]

I have 2 issues here:

1. How do I make sure that both the conditions run inside the branch or how do I restructure it?

2. If my lookup has 5 issues, it is creating 5 new tickets, but I want only 1 ticket to be created. this is because it is "for each issue". how do I solve this?

Let me explain my automation flow once: 

Scheduled Trigger
└── Lookup recent issues
    └── For each issue
        ├── Create firmId variable
        ├── Lookup 90-day issues for firmId
        ├── If > 4 issues
            ├── Lookup existing Tickets
            ├── If Ticket already exists for the firmID → Edit and link issues
            └── If not → Create new ticket

So basically, I am running a scheduled JQL trigger, and storing firmID from those tickets. Then I am checking if the firmID is used for more than 4 issues in lookup. 

if it is more than 4, then there are 2 conditions:
if ticket already exist, then link trigger ticket to existing ticket
if ticket doesn't exist, create a new ticket




I have 2 "IF" conditions in a single branch. Once the first "IF" condition fails, the second one is not even checked for. How do I make it to check for both if conditions? 

this is the audit log. it exits after if lookup > 0. but my 2nd IF condition is IF lookup = 0. 

[Mikael Sandberg]

What you see is expected, IF conditions are evaluated sequentially the way your rule is currently configured. Currently For each branches don't have access to IF/ELSE conditions, you you would need to reconfigure your automation. One way would be to call a second automation that does the actual work and use the IF/ELSE condition there.

[Bill Sheboy]

Hi @Manav Shah 

Adding to the suggestions from @Mikael Sandberg ...

If / Else Condition blocks cannot be used inside of branches, but branches can be used inside of If / Else blocks.  Perhaps restructuring the rule will help, and...

What problem is your rule trying to solve?  That is, "why do this?"  If you explain your scenario that will help the community suggest alternatives.  Perhaps like this:

GIVEN some initial condition
AND some other initial condition
WHEN I do this thing
THEN perform this action

Kind regards,
Bill

[Bill Sheboy]

Thanks for that additional information, @Manav Shah 

You do not show your entire rule, and from what you describe, I wonder if you could use the Scheduled Trigger with JQL to find the "recent issues" rather than a lookup.  Then the trigger would handle the iteration rather than branching.

For example:

• trigger: scheduled, with JQL for your "recent issues"
• action: lookup issues, with JQL to identify the "firmId" related ones
• if / else block
  • now you can test the lookup issues result for each condition...
• else / if ...

[Manav Shah]

@Bill Sheboy  @Mikael Sandberg 

[Bill Sheboy]

@Manav Shah -- Does the updated rule work as you expected?

If not, the latest rule image you show still uses a branch, and so the if / else block cannot be used inside of that.

[Manav Shah]

I have just send screenshot of my current workflow.

Can you explain me how can I update my rule using your logic? If possible bit step by step

[Bill Sheboy]

I did see your updated rule, and that is why I noted to please see the earlier suggestions as I believe they have what you need:

• When you want to use the if / else block, that cannot be inside of a branch
• Instead, use the Lookup before the if / else block, and then branch inside (if necessary)

[Manav Shah]

@Bill Sheboy @Mikael Sandberg thanks for your responses. I have updated my query in a bit detail now. Please let me know if you are able to understand my issue and help me out