Issue Created automation isn't working when story is cloned from another project

[GlenellRosburg]

I have created a request form for end users to complete in a team-managed Jira project. When the request is created, the team-managed story is cloned to my company-managed project. I have added an Issue Created automation to change the default priority. 

The automation doesn't trigger when the new story is added to my company-managed project. The automation does work when I clone a story within the company-managed project. 

Can you help me understand why this automation doesn't work for my team-managed cloned story?

 

[Bill Sheboy]

Hi @GlenellRosburg 

Please also post an image showing the complete audit log, and audit log details for the rule execution, to provide more context for this symptom.

How is the new story added to the project?  Is another automation rule creating it, a person doing it manually, or some other method?

What is the scope of this rule?  Is it defined for only the company-managed project scope or is it multiple project /global?

Finally, for rules using the Issue Created trigger, I recommend always adding the Re-fetch Issue action immediately after the trigger.  That trigger can fire so quickly that some issue data may not be available to the rule yet.  This can lead to condition or rule action errors.

Kind regards,
Bill

[GlenellRosburg]

The new story is created by automation. Here's the team-managed automation to clone the ticket to the company-managed project. 

Here's the company-managed automation to change the Status and Priority. This works if the company-managed story is cloned within the same project. As you can see from the Audit Log the automation is working.

This rule is only for this 1 company-managed project.

Can you explain how to add a re-fetch issue action immediately after the trigger?


Thanks!

[Bill Sheboy]

Thanks for that additional information, @GlenellRosburg 

The Re-fetch Issue action may be added from the list of actions.  Here is the documentation on it: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Re-fetch-issue-data 

Just select that line under the trigger issue and the plus-sign + to Add Component will appear.  Then select the Re-fetch Issue action.

Based on what you described, it seems the issue cloned by another automation rule is not triggering your rule to change Priority.

By default, the actions of one rule cannot trigger others.  This is to prevent mistakes and run-away rule looping. 

When you intentionally want the actions of one rule to trigger another, in the "downstream" rule, look in the details at the top to enable the allow rule trigger option:

Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule.

In your case, I believe that is the rule triggered on Issue Created to change the Priority.

[GlenellRosburg]

I don't understand why the company-managed story doesn't appear as a Created issue. It is a new story with a unique ID.  Why would the system not recognize the story as new story? When I clone an issue within the company-managed project, it is recognized as a new story.

[Bill Sheboy]

In my last post, did you see my note about the allow-rule-trigger option?

If an automation rule creates the issue, that event cannot trigger another rule unless the allow-rule-trigger option is enabled.

[GlenellRosburg]

Checking the allow-rule-trigger option fixed this. THANK YOU!

[Bill Sheboy]

Awesome; I am glad to learn that helped!