Reputation: 1800
We have several, independent teams that have their own priorities and work. Yet the teams are all on the same code-base, so when we deploy, everyone's code goes out at the same time.
How have you dealt with this using Jira?
A couple of possibilities come to mind:
Upvotes: 7
Views: 4485
Reputation: 21
For those interested: 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 propagated.
https://marketplace.atlassian.com/plugins/net.collabsoft.plugins.jira.jira-version-sync
Upvotes: 2
Reputation: 649
There is an existing JIRA for this at https://jira.atlassian.com/browse/JRA-2698 which you can vote for and wait patiently til the end of time.
There are a couple ghetto ways you could do this without coding:
Upvotes: 2
Reputation: 5575
I am not sure if there is an out of the box solution for this problem, but you can automate version creation across projects via Jira Command Line Tool.
Upvotes: 0