Why is my automation to add a new issue to a Sprint board not working?

[Phil Bustin]

From an Epic, I created an issue.  My automation (below) isn't firing.  When I create the issue, Project in the Epic and the created issue = the value in the automation.

Automation

[Trudy Claspill · Accepted solution]

Hello @Phil Bustin 

Please share with us the details of the Audit Log for the execution of the rule.

Is the Sprint field in the issue blank after this automation runs or does the field show the sprint value you expect?

What is the Filter Query for the board you are referencing?

[Phil Bustin]

The log shows "No execution".

A different automation works, based on a different field, not Project, but that field is selected by the user in a transition form preceding an automation clone action.

[Trudy Claspill]

Can you please provide a screen image of the Audit Log? Is there not an entry, indicating that the rule was not triggered? Or is there an entry that has some Status and some messages when you expand the details (Show more).

You did say in your original post that the rule "is not firing". The rule trigger is for "Issue Created". That trigger has no conditions associated with it directly, so the rule should be triggered when an issue is created in the project that is specified on the Rule Details page in the Scope area.

Is the newly created issue created by a user through the UI, or is it created as an action in some other rule?

By default when you create a new rule it is configured so that it will not be triggered by actions that are executed by other rules. 

If the newly created issue is created by an action in another rule, then this rule (the one you showed in your original post) needs to have an option on the Rule Details page set:

[Phil Bustin]

Well, I wrote a lot below, but the automation is working now.  I'll leave my treatise in place just for fun:

I discovered that the automation (let's call it Automation A) worked twice and then there was no action (see below).  

The newly created issue is created from an epic by a user; not created as an action in some other rule. 

There is, however, a different automation (let's call it Automation B) that can create the same issue type in a clone action, from an JSM issue type identified as a condition in Automation B.

I created an issue just now with Automation B, and it did not fire Automation A.

Automation A log to date