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:
- Keep the original issue open with sub-tasks for each site until all sites are updated. Problem: Tickets linger in multiple sprints.
- Create separate tickets for each site that needs to be updated. Problem: End up with ticket bloat.
Are there any other approaches to managing multi-site deployments?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.