Automated Release is not triggering the Trigger Version Released

[Christopher Macnichol]

This issue is a little confusing to me.  I have Automation for Jira Cloud and for the most part it works great.  However, in this case, one of the triggers does not appear to work as I would expect.

I currently have setup two separate related Automation.  The first, on a scheduled date, will trigger an Auto Release of the next un-released version.  This works perfectly.

However, the second Automation, which is supposed to trigger on "Version Released" never triggers.  If I manually release the version, it works exactly as designed.  It just does not appear to work on the automated release.

Is this by design?  Am I missing something?  I may be able to switch the second to a scheduled trigger as well, but I had planned on being able to access the Version Released name in the second workflow.

[Bill Sheboy · Accepted solution]

Hi @Christopher Macnichol -- Welcome to the Atlassian community!

This sounds like a timing issue with the rule firing.  Please review your second rule's details, and check the option to "Allow rule trigger".  This will enable the action of the first rule to result in a trigger of the second one.

Best regards,

Bill

[Christopher Macnichol]

You called it.  I somehow completely overlooked the option to let it be triggered by other rules.

Been getting a crash course in Jira and automation the last two weeks, so I will count myself lucky if that is all I missed  :)

Thank you for the help, much appreciated.