要約

Currently, the versions in Jira Cloud are specific to each project. This is being tracked as a feature request - JRACLOUD-66760 : Ability to pick Version from another Project

ソリューション

Despite the current limitations, Jira Automation allows to copy the versions as suggested in the below-mentioned use cases:

1. Create new versions in one project and copy them in another project(s)

   • Rule scope: Set up a Global or Multiple projects rule. For a Multiple projects rule, select the project where the version will be created and other projects where it is to be copied.
   • Trigger: Version created

   • New condition: Advanced compare condition. The below mentioned condition uses the project SOFT1, where the version will be initially created. You can update it accordingly.

     {{version.project.key}} equals SOFT1

   • New action: Create a version in the desired service project
     
     
     

2. Copy specific existing versions from one project to another

   • To copy specific versions from one project to another, restructure the automation rule suggested above and change the trigger to Version Updated. Then, open the desired version in Edit mode and click on Save without making any changes. This will trigger the automation rule.
     
     

3. Copy all the existing versions from one project to another

   • To copy all existing versions from one project to another, create an automation rule as suggested in "How to copy version releases from one project to another using Automation for Jira"

References: 

1. Automation smart values for version
2. Version triggers in Automation: Version created, updated, released 
3. Managing versions in Jira cloud

If you encounter issues or require further clarification on the topic, please consider reaching out to Atlassian Support for further assistance.