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?

0 comments

Comment

Log in or Sign up to comment
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published May 21, 2018 in Jira Software

How large do you think Jira Software can grow?

Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...

1,209 views 10 18
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