Forums

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

Automation not working for one project

Marius Skoglund
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 17, 2023

Hi

I have some automation rules for a software project, these rules should change fields upon ticket creation. However, the audit log shows no event other than configuration changes.

The rules are project specific and confirmed within the right project scope.

Rules are triggering normally for other projects.

I suspected a missing Issue Created event, and added this to the transition to status: New, but no luck.Schermafbeelding 2023-03-17 162343.pngSchermafbeelding 2023-03-17 162316.png

Are there other logs that can tell me why this is or isn't happening?

2 answers

1 accepted

0 votes
Answer accepted
Marius Skoglund
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 20, 2023

This has been solved. It was a long week and I was working with many workflows. I added Issue Created event to the wrong workflow.

Added Issue Created event to the correct workflow and automation is now firing correctly.

0 votes
Marco Brundel
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 17, 2023

Hi @Marius Skoglund ,

Does the rule work if you remove the condition on Status?
Can you add a screenshot of the Rule Details?

Is the Epic created by a user or by another automation rule?
If it is by an automation rule look at 'Allow rule trigger' in rule details

Regardless of your question, my advice is to see if you fill in a specific custom field when creating an Epic and use "Field Changed" (on create issue) as a trigger with this custom field. Then the rule only goes off at the intended Epics. Saves a number of unnecessary rule starts.

Regards, Marco
Screenshot 2023-03-17 at 16.57.02.png

Suggest an answer

Log in or Sign up to answer