We have a web site that is used by a limited group of administrators and managers. To manage user load, we have three independent production environments. Production A - Setup for Enterprise Client A. Production B - Setup for Enterprise Client B. Production C - A Multi-tenant site for smaller clients. We'll typically release to with Production A, B, or C depending on who had the most tickets in the sprint, let the release sit on that production server for a few days and then release to the other two.
I have been using the JIRA release hub to manage releases, which seems limited.
What suggestions do people have for me to let my folks know when a particular issue is released to Production A, Production B and Production C.
If you are managing multiple releases across multiple team/sprints, I'd recommend using Cycle Control. You can define a release type which follows your own processes and use stages for specific hand-off between teams (which I assume is your case scenario, correct?). The app offers several types of intermediate checkpoints (e.g. quality gates, milestones, approvals, checklists) which help you coordinate deliverables between teams.
There are other features that can help streamline your release management process, but this one in particular can solve your issue.
If you need more information, ping me :)
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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