Is there a way to have the fixVersions cross project in Jira?

We have several independent groups that have their own priorities and work. However, all commands are on the same code base, so when deploying, each code exits at the same time.

How did you deal with this with Jira?

Several possibilities come to mind:

  • if there was a cross-project fixVersions, this would be ideal, since each version would be synchronized.
  • we could use tags and update all filters that everyone uses to segment what people see.
  • we could manually synchronize fixVersions, ug
  • we could use their API to manage fixVersions to synchronize them
  • something else completely
+4
source share
3 answers

There is an existing JIRA for https://jira.atlassian.com/browse/JRA-2698 that you can vote for and wait patiently until the end of time.

There are several ghetto methods that you could do without coding:

  • Ask them to share the same project, but use the Component drop-down list to separate the work.
  • Using the new Greenhopper, at least you can have a cross-project sprint, and then you just need to have a manually synchronized version for projects.
+1
source

For those interested: we just launched the Version Sync add-on for JIRA to the Marketplace, which will do just that. It will automatically keep versions in sync between several projects, where you have one β€œMaster” project and an unlimited number of related projects to which version changes apply.

https://marketplace.atlassian.com/plugins/net.collabsoft.plugins.jira.jira-version-sync

+1
source

I am not sure if there is a solution for this problem, but you can automate the creation of project versions through the Jira Command Line Tool .

0
source

All Articles