I'm using Jira to track some projects that are related to my main development project and I'd like to use the same same set of versions for several projects. For instance, in my main development project, DEV, I have the versions 7.0, 7.1, 7.2, 7.3, 7.4, etc.I also have a customer support project, CSI, and an equipment request project, ER. I'd like to have the version list in the DEV project mirrored in the CSI and ER projects so I don't have to maintain multiple identical lists. Does any one know how to do this automagically?
A perfect solution would be to define a set of rules that would create a subset of the versions in the DEV project and use that subset to populate the version lists in CSI and ER, but I kinda doubt that's possible or practical.
Since the version are different entities in different projects, you will certainly need some programming to keep them in sync.
You can either write a plugin (a service or something) that checks for new versions and sync them or do it using remote APIs like SOAP/REST or using JIRA CLI and keep the logic outside of JIRA.
You can also look at creating a new admin operation which creates a version in multiple selected projects but that will be a plugin too.
Whats about Issues I have to move between projects. I want them to keep the version information, especially the affected versions. If these versions are different objects, What happens during move?
Just came across this and you might have already know the answer by now. Just sharing this KB here for others to refer to:
That's what I ended up doing. I wrote a script that used copyVersions to copy selected versions from the base project into the others. Until I can write something that will auto-sync versions I'll have to remember to run the script.
@Byron: I don't know if this is still an issue for you, but we have just launched our Version Sync add-on for JIRA to the Marketplace that will do exactly this. It will automatically keep versions in sync between multiple projects, where you have one "Master" project and an unlimited number of linked projects to which version changes are propgated.
Question: Does Version Sync allow multi-project reporting against a single version? I want to use the Version Report and Release Burndown reports to monitor progress toward delivery of a product being developed under multiple JIRA projects. It won't be useful to me if Version Sync only creates same-name versions in the separate projects.
I can only recommend to stay away from VersionSync and ComponentSync plugin. They are buggy and there is zero support from the vendor. Reported to Atlassian already. Don't use, don't waste your money.
When I hosted my own JIRA I was using versionSync and I never had a problem with it. It made my life way easier trying to manage multiple JIRA projects tied to the same version releases. I switched to JIRA Cloud though and now have to do it manually which is a pain.
I know it's an old thread but if you've created a script for it shouldn't you be able to use the script runner to trigger it at your own schedule?
Perhaps not present in cloud version?
The reason this doesn't seem to exist is that JIRA wants to upsell you into using their project planning add-on and use the "Releases" field (which uses fixVersions anyway)
Version sync has some major draw backs. Once you turn on version sync, nobody can add a version to a project that is set to sync. It is common to only want to sync certain versions. I used release dog to do the sync. It still works and it is free, but it has bugs in the latest release in that it doesn't sync changes anymore.
If you go the Project settings page of the "master" project (which is the source project from which you want the versions to be propagated to "linked" projects) and click on "Add project link" in the Version Sync panel on the summary page a model will open. This model will allow you to create a project link. After you have selected the projects you want to link, you will have the ability to select the type of synchronisation:
If you select "specific changes" the add-on will no longer limit the ability to add or modify versions. Keep in mind, that if you select all options, it will work the same as it would in "Full Synchronisation" mode.
Yeah I found it. But in order to get the create back on a given project, you have to uncheck "create". Which means that any new releases created in the base project will now not be created in the other projects. What is needed is the ability to chose which projects sync and which ones don't, and still allow teams to be able to create their own releases. Thanks for the help, but I think I'll stick with the free Release Dog plugin for now.
Hmm... that should not be the case. You should not have to uncheck the "create" button to unlock the ability to create new versions in the linked projects. It would defeat the purpose of the add-on. We will look into this first thing Monday morning to confirm if this is an issue and fix it!
That may have been my misunderstanding. I thought I had to uncheck the create. I checked it and it is working now. However it seems to be doing the wrong thing still. I created a new release in the project that is getting synced to. I have the delete option syncing on the main project because if I delete a version in the main project I want it to disappear on the other projects. However I want to keep any local projects that were created. But it is deleting them because they don't exist in the main project. Seems like a strange behavior to me.
Yeah, that has been an interesting "feature" of the add-on. The problem lies with the fact that in the past, Jira has been unreliable in regard to the VersionDeleted event. So if that event was missed, the version would not have been deleted, causing the same confusion the other way around (expecting the version to have been deleted, only to find that it wasn't). The solution was to add a background synchronisation that replay the events if they were not properly executed. The downside is that this means that enabling the "Delete" option automatically removes any versions from linked projects that are not available in the "master" project.
With every major release we are re-evaluating how we can improve on this issue, and would really appreciate your input!
If you want any more feedback offline I am happy to provide it. I am a release manager for my company and this is a huge pain point. I don't mind paying for a plugin, but it would have to meet my needs.
Hi @Anil Kumar2,
There has been a feature request dating back to 2003 (https://jira.atlassian.com/browse/JRASERVER-2698) which was resolved by Atlassian last year in which the Jira product management team has indicated that they do not consider this to be a core functionality.
So I'm afraid you will either have to script something (using the Jira API, the really great Scriptrunner add-on by Adaptavist or Jira Command Line Interface by Bob Swift / Appfire) or use our add-on.
I did try the version sync option one time as well. What I didn't like about the version sync was that you couldn't also have unique releases in the same projects that are setup to sync. I would consider version sync if they allowed only syncing of certain versions, but once you setup a project to sync, it syncs every version.
If you have portfolio, they have an option to create "shared releases" over multiple projects. But it is a little cumbersome to use. Those are the options that I know about.
Hi Atlassian community, My name is Max and I work on the product integration team at Atlassian. I am pleased to announce the early access program for the Jira Cloud add-in for Outlook. This add-in...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events