Automation - Ignore action error OR check if version exists

[Ray Nixon]

Hi, 

I have an automation that is triggered when a version is released, it checks what project the version was for, and then releases identically named versions in a few other projects.

The problem is those versions don't always exist. How can I either, check if a version exists in a project, or mark an action (release version) as ignorable if there's an error?

[Bill Sheboy]

Hi @Ray Nixon 

For a question like this, context is important for the community to help.  Please post the following:

• what type of project is this (e.g., company-managed, team-managed, etc.), 
• an image of your complete automation rule,
• images of any relevant actions / conditions / branches, and
• an image of the audit log details showing the rule execution.

Until we see those...

How you solve this depends upon if there are always issues assigned to the versions (i.e., Fix Versions field) in the other projects, or not:

• Using the if / else block, and when there are always issues assigned to the other versions, one could use a JQL condition to find any issues in the version and only proceed if some are found
• When assignment is unknown, the rule would need to use the REST API endpoint (called with the Send Web Request action) to find any matching versions and then release them...possibly also using the REST API.  This approach would allow looping over the possible projects with an Advanced Branch to find / release each one.

Kind regards,
Bill

[Trudy Claspill]

Hello @Ray Nixon 

To better enable us to advise you, can you please provide screen images showing your entire automation rule and the details of each step?

Is the rule scope Global or specific Projects?