Issue Summary

When an automation rule is configured with a global scope and the release versions action is used, the action does not return the project versions because the rule cannot determine the appropriate project context. This issue does not occur when the rule is scoped to a specific project.

Steps to Reproduce

• Create an automation rule with global scope that triggers on "when version is released" and attempts to release existing versions in a project.
• Use smart values (e.g., varVersion.name) or hardcoded version names (e.g., 7.0.0) in the "Release version" action.
• Execute the rule by releasing a version.

Observe that the intended versions are not released.

Suggestion

Support the ability for the automation rule to be able to infer or determine the correct project context for the version and successfully execute the "Release version" action when the rule scope involves multiple projects

Workaround

Call the Jira REST API endpoint to release versions via a "Send Web Request" action component