Automation for Cloning (copying) a fixversion from one project to another?

[Misty Meyers]

Is it possible to "clone" or copy a fixVersion (release) from one project to another?  My team has multiple projects for Development, but we maintain a single Jira project for all the testing.  I was hoping there was a way, that when a new fixVersion (release) is added to one, the same would be "copied" and created to the Test project.  We don't need all the related work, just the mere fixVersion.

example:

Project A creates anew release: ios release xyz, then automation creates on the QA Project a release with that same name

I'm thinking it's not possible, but hoping!!

Thank you!

[Walter Buggenhout · Accepted solution]

Hi @Misty Meyers,

I actually found a slight hack to make this work. My automation rule looks like this:

The hack relates to the for JQL branch that is needed with the Version created trigger of the rule. In order to use the version smart values to create a new version, you need to provide a list of issues in order to proceed.

There is an issues in version branch available, but on a version created trigger there are no issues. So I used the JQL branch to enable actions, but since you want to create the version only once, you should ensure you only return 1 issue. Hence, I defined a filter that only returns one issue (always). If your JQL branch returns more issues, you'll notice some errors in your audit log as the rule would try to create several versions with the same name.

Hope this helps! 

[Misty Meyers]

Thank you Walter!

Do I have this correct; when a version is made the version is also made on the  Kanban sample project. Therefore, this automation rule would need to be added to each of the Jira Projects?

[Walter Buggenhout]

Hi @Misty Meyers, you can make the automation rule a global rule. In the configuration of the rule, you can specify which projects it applies to, but indeed, given your scenario it must be enabled for all projects where you want to detect the (potential) creation of new versions.

[Misty Meyers]

Thank you again!

I'll give this a little test! :-)

[Kelly Arrey]

Here's my rule. I was able to get this working without your hack Walter.

[Misty Meyers]

Hi Kelly,
Question on your magic above. I wasn't following the purpose of the "And Create Version." I understood the first as when project ENG adds a release creates that same release on project DOC. What am I missing in my understanding?
Thank you!!

[Kelly Arrey]

Hi Misty, I have 3 "Create Version" clauses because in our use case, I'm propagating the Release Name from ENG to 3 other projects, i.e., DOC, PM, and REL.

HTH,

Kel

[Anette Unger]

I can choose only ONE Project. It is the same like I create the rule (globale). How it is possible choose other Projects like you (3)?

[Kelly Arrey]

Hi @Anette Unger, as you say, we can only choose one project at a time in the "Create Version" action, so that's why I have 3 separate "Create Version" actions in my rule (please see my screenshot above). The rule is a global rule which has to be set up to operate on all the relevant projects, e.g:

HTH, 

Kel

[Marlene Kegel - codefortynine · Accepted solution]

Hi @Misty Meyers,

I am Marlene from codefortynine.

If you're open to try a Marketplace app, you could check out Version Sync for Jira.

Our app allows you to sync versions between Jira projects. You could either sync them bidirectionally, or to a specific target project.

It's also possible to manage shared version in the Version Sync - Release Overview.

You can read more about our app, in our documentation.

[Misty Meyers]

Hi Marlene,
Thank you.  That looks promising. I forwarded the link to our overall Jira Admin to review.

Appreciate you pointing it out!

[Marlene Kegel - codefortynine]

You're welcome, @Misty Meyers. Don't hesitate to reach out to our support if you have questions or feedback.