Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation rule is not running all actions

Cheryl Hill April 14, 2025

I have a pretty basic (I think) rule that runs when an issue (customer bug) is created. It is supposed to check two different fields to see if they are empty. If they are, then put something in them and move on finishing with sending the entire issue to Microsoft Teams. It BREAKS/STOPS when one of the conditions is not met and it never moves onto the next question, nor does it send everything to Teams.

What it should do is:

1. When an issue is created...

2. If the issue is Customer Bug

     a. Check if description is empty

          i. If yes, edit the description field.

          ii. If not empty, just go to next check. THIS DOESN'T HAPPEN. THE RULE STOPS before doing 2.b or 2.c!

     b. Check if "steps to reproduce" is empty

          i. If yes, edit the "steps" field

          ii. If no, go to Teams integration. THIS DOESN'T HAPPEN. THE RULE STOPS before doing 2.c!

     c. Send to Microsoft Teams

3. If anything other than customer bug ... leave this rule.

How do I get it to do each step and not stop?

CustomerBug-CreateAutomation.png

 

1 answer

1 accepted

5 votes
Answer accepted
Mikael Sandberg
Community Champion
April 14, 2025

Hi @Cheryl Hill,

Welcome to Atlassian Community!

The way you have configured the automation it is expected that description has to be empty before moving on to the next action. The way you describe it sounds like you want the automation to continue even when description is not empty. If that is the case then you would need to use the IF/ELSE condition, this will create a branch and would allow the automation to continue to the next action even if description is not empty. 

Cheryl Hill April 14, 2025

Thank you Mikael, I get the concept of what you're saying, but my ELSE is just do the next thing. Is this how it should look?
Rule-changed.png

Mikael Sandberg
Community Champion
April 14, 2025

Yes, that looks good. The only thing I would add before the Team message would be a refetch, that way you would get the change to description and reproduce if they are updated by the automation.

Cheryl Hill April 14, 2025

Yes, I had planned to re-fetch. This seems to be working now. Thank you so much!

Like Mikael Sandberg likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events