Transfer releases including issues from one project to another

Question

Hi,

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

Thanks!

Mark Segall · Answer

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

* Create a project to serve as a central source of truth for your releases
For this example, will call the project RELEASES
* 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
* Create two similar automations to enable version syncing:* When version is created, create that version on the applicable projects
* 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}}

aamelyan · Answer

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 · Answer

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.