No longer able to insert an "issue fields condition" within an "if/else block"

[Doug Levitt]

I have several automations which include an "issue fields condition" inserted within an "if/else block".

Below is an example:

For whatever reason, the editor doesn't allow me add another component (effectively a 2nd "Issue field condition") where the Black Arrow is (above).

I tried to recreate the same automation from scratch.  And it wouldn't allow me to include a single Compare operation following the Lookup operation.  The only options were: Advanced Branching and Branch rule / related issues.

Anyone else running into this problem?  It significantly limits the range of things I can do.  Yes, I realize there are workarounds for this specific use case.  But my automations are quite involved.

Is this a bug that was introduced?  Or, was this purposely implemented to restrict these use cases?

Thanks,

Doug

[Andreas Knecht · Accepted solution]

Hi there,

Apologies but this is indeed a bug: https://codebarrel.atlassian.net/browse/AUT-2350

We'll let you know once a fix is available. For now the work-around is to drag a condition onto the if branch as mentioned above.

Cheers,
Andreas

[Doug Levitt]

Hi @Andreas Knecht 

Thanks for your reply.

As a note, https://codebarrel.atlassian.net/browse/AUT-2350 (and the related https://jira.atlassian.com/browse/JSWCLOUD-22414) were created back in Jan, 2022.

But, I was able to create my rule (see code snippet above) on May 31, 2022.  At that time, the rule editor allowed me to add a condition (actually multiple) inside an IF Branch.  But now it doesn't.

Thankfully, there is that work-around. 

Thanks,

Doug

[Bill Sheboy]

Hi @Doug Levitt 

I recall another post about this months ago, and the person noted they could do this by creating the condition outside of the if/else and then dragging it inside with the rule editor.  I just tried this and it still works...However...

As the rule editor does not offer adding the condition this way natively, I would test fully to ensure it works as you expect.  If it does, Perhaps log a defect to Atlassian for the editor problem/limitation.

Kind regards,
Bill

[Doug Levitt]

Thanks @Bill Sheboy for the head's up.  I will log a defect with Atlassian.  This previously worked.  So, it sounds like it's just a bug they recently introduced.

Doug