It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
Community showcase
Published in Jira Software

[New] Jenkins for Jira Software Cloud and a way to connect your hosted apps

Jenkins is the leading open-source automation server used by startups and enterprise teams to build, test and deploy code to production.   We are excited to announce an official integration betw...

1,055 views 1 15
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you