We have ~10 sites that run on the same software platform.
Our current JIRA workflow involves a single Project that contains all issues. Each issue is tied to a Release (Fix Versions) that specifies when that particular issue will be rolled out to Production.
Most of these issues are not released to all sites at once. We generally release to a single site first and then, at some point in the future, update the remaining sites.
This causes a problem: Because the original issue is closed immediately upon the first release, we have no way to simple way to document that it still needs to be deployed to other sites.
We thought of two solutions, neither of which seem great:
Are there any other approaches to managing multi-site deployments?
...It's true that there are projects in Jira; but they are merely a way to cut off issues, to tell them apart from other sections of work and to apply rules that are specific to that team (the schemes)....
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs