What is the best way to manage multi-site releases for issues?

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:

  1. Keep the original issue open with sub-tasks for each site until all sites are updated. Problem: Tickets linger in multiple sprints.
  2. 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?



Log in or Join to comment
Community showcase
Bridget Sauer
Published Mar 05, 2018 in Jira Software

Jack Graves: Real Ale enthusiast with a knack for Jira Software implementation

@Jack Graves first caught our eye with his incredible breakdown of what, in his opinion, can make or break a Jira software implementation. (Read his thoughts on this thread)! In this followup Sh...

62,790 views 4 6
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot