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.
Just came across this and you might have already know the answer by now. Just sharing this KB here for others to refer to:
It's absurd that we have to pay for another plugin for this! This is definitely a feature that should be out of the box - no doubt about that.
I read some comments and people are suggesting to have the same version created across multiple projects using a script or whatever but I just wanted to emphasize that even if you do that, at the end of the day each Release/fix version inside of each project stands as their own independent entity - even though they will all have the same name.
Most of the time, this solution is not satisfactory as many reports and data you'll extract from Jira will not be able to consolidate all those fix versions into a single one.
So this solution, even though it kind of helps, it's still far from the ideal solution.
I'd suggest you vote for the feature request with Atlassian instead.
Don't tell me Atlassian Advanced Roadmaps plugin comes to solve this because we have it and it still hasn't solved this problem.
Hello Atlassian, anybody there??? Gosh, we shouldn't have to be preaching to the choir!
Using third party companies to deliver basic features is shameful, all I'm saying...
@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.
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!
Hi @Anil Kumar,
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, @Oscar Reques. On the surface, your comment seems a little unfair.
The enterprise editions of Jira, for both cloud and on-prem platforms, include Advanced Roadmaps.
Beyond that, like many platform providers, Atlassian has developed a rich ecosystem of 3rd-party app developers that add all kinds of capabilities to Jira (including Gantt, and portfolio management). Most of these run on all editions of Jira.
Maybe you can share some additional details about your specific circumstances.
-dave [ALM Works]
P.S. Full disclosure, my company makes one of the more popular Gantt / PPM solutions for Jira. However, the links I included above will guide you to all of them. There are many choices.
Dear @Dave Rosenlund _ALM Works_ , please feel free to come to my cousin's car shop. He will sell you a wonderful car.
Later on, you will discover that although it's a car, you need to pay additionally for the steering wheel.
But don't worry, the enterprise edition of the car, includes the wheel, for both gas and electric car versions (even hybrid !!)
Beyond that, like many car sellers, we have developed a rich 3rd party complement providers, where you can get other kind of missing capabilities like ash tray, copilot side mirror, music speakers...
My comment may be unfair of course, as unfair as a company trying to monetize very basic features that are not innovations, obviously.
Anyway, thanks for your time reading and answering Dave !!
Have a good day
BTW, I think your analogy works perfectly.
Someday, maybe Gantt and Portfolio Management will become part of the base model, but for now, they are part of the luxury model only. To get these features some people will opt for that model, while others will choose the aftermarket approach (so they can get exactly what they want at a better price point).
Good luck with your decision,
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