Can a component be added AFTER an If/Else block (so it is executed in all cases)?

Tzirel Shaffren June 21, 2023

I have an automation rule that is triggered on Issue Creation, and if Assignee is empty, it sets the value based on a custom field. It is a series of If/Else blocks

What I would like to be able to do: In the same automation rule, AFTER the If/Else block is finished, set another custom field based on the Assignee setting.

What I have tried: 

  1. Creating another rule that has "allow other rule actions to trigger this rule" checked. It is triggered by Issue Creation + Assignee not empty. It does a re-fetch and then sets the second custom field based on Assignee. It didn't work.
  2. Adding a re-fetch and setting the second custom field in every single block after Assignee is set. This works, but is very inelegant and hard to maintain.



1 answer

1 accepted

2 votes
Answer accepted
Adam Rypel _MoroSystems_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 21, 2023

Hello @Tzirel Shaffren ,

You should be able to do this:

Snímek obrazovky 2023-06-21 145027.png

You should be able to add the components after if/else without a problem. Or have I misunderstood?


Tzirel Shaffren June 21, 2023

Thanks so much for your quick answer!

You exactly understood what I wanted. For some reason it didn't work for me. But now I will try it again with the help of your image and see if I can get it to work.

Tzirel Shaffren June 21, 2023

Works like a charm - thanks!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events