Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Transfer releases including issues from one project to another

aamelyan September 5, 2023

Hi,

We need to transfer (move) our completed releases from one project to another. Is there a way to do it?

Thanks!

1 answer

0 votes
Mark Segall
Community Champion
September 5, 2023

Hi @aamelyan - Releases are specific to each project so you need to recreate the desired releases in the target project and release/archive accordingly.  Once you've done that, you can move your issues and it will retain the Fix/Affects version fields. 

aamelyan September 5, 2023

Well, I was looking for the same functionality that we have for issues where you move the release form one project to another. I also found question, but I yet to hear how this works using the add-on.

https://community.atlassian.com/t5/Jira-questions/Transfer-release-versions-to-other-projects/qaq-p/952835

Mark Segall
Community Champion
September 5, 2023

In scenarios where I have multiple projects that need to share the same release structure, I have gone this route:

  1. Create a project to serve as a central source of truth for your releases
    For this example, will call the project RELEASES
  2. Create a dummy task on each of the desired projects with some way of identifying that this project is in scope for releases (e.g. a very unique Summary, a label, a custom field, etc.)
    For this example, I'll use the label RELEASE
  3. Create two similar automations to enable version syncing:
    1. When version is created, create that version on the applicable projects
    2. When version is released, release that version on the applicable projects

RULE #1 Version Created

  • RULE DETAILS: Global Scope rule
  • TRIGGER: Version Created
  • CONDITION: Project = RELEASES
  • BRANCH (JQL)
    • Labels IN (RELEASE)
    • Create Version
      • Version Name
        • {{version.name}}
      • Release Date
        • {{version.releaseDate}}

RULE #2 Version Released

  • RULE DETAILS: Global Scope rule
  • TRIGGER: Version Created
  • CONDITION: Project = RELEASES
  • BRANCH (JQL)
    • Labels IN (RELEASE)
    • Release Version
      • Version Name
        • {{version.name}}
      • Release Date
        • {{version.releaseDate}}

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events