Can I add an else to a rule condition, and how?

[Phil Bustin]

I created the following rule, but I can't figure if and how I can add an else condition to the last condition (To Region is one of BA, MO).  The new condition could be (Else), although (To Region equals PA) would also work.  For the  new condition, the action would be (Then: Transition the issue to PA Certification).

If it is relevant, I don't know whether our product plan is Free or not.  We don't have automation add-ins.

[Bill Sheboy · Accepted solution]

Hi @Phil Bustin 

This is the second question I have recently seen with this need (if/else in a branch) and I thought this was possible, and it is not currently.  The UX of the rule designer appears to have recently changed to make it more clear when if/else can be used.

For the use case you are showing, a couple of possible work-arounds would be:

• Easy way: Use different branches over all sub-tasks, including conditions for each region set/query.  This would work as long as they are not dependent upon each other for action results.
• Harder way: Use different branches, over the exactly matching sub-tasks.  This could be done using advanced branches and smart value, list filtering on Status and Region, and then iterating over any matching sub-tasks.

Kind regards,
Bill

[Kelly Arrey]

@Bill Sheboy @Phil Bustin Sorry, I'm not following.  I see this:

Which, when included yields:

I would have thought that was what you were looking for? What'd I miss?

Thanks,

Kel

[Bill Sheboy]

Hi @Kelly Arrey 

I believe Phil wanted to use an if/else structure inside of the branch, not outside of it.

I believe there was a "hack" where these could be created outside of the branch and then drag-and-dropped inside.  That unplanned/unpredictable behavior appears to have been removed.

Kind regards,
Bill

[Phil Bustin]

If it can be done using a branch, I'll attempt that.  New to all of this.

[Phil Bustin]

Today, I can't find where to create a branch in my rule.

[Phil Bustin]

I'm back to square one: I need a rule for a sub-task (issue type = Dev Task), so that when it is transitioned (there is only one transition), its parent is transitioned to a particular status.  What would that rule look like, please?

[Bill Sheboy]

Hi @Phil Bustin 

As that seems like a new use case, I suggest creating a new question post for it, and link back to any relevant ones for context.  Otherwise only the people following this current thread will see it to offer suggestions.

Kind regards,
Bill

[Phil Bustin]

Good advice.  Done.