JIRA Tickets in different Statuses for different Deployments

[Andy Kimbrey]

We have a Product which is deployed across 9 different geographical zones (eg, EU, USA, Asia).

We deploy our Product to one zone at a time, so a JIRA ticket may be in Live Status in the USA, but be in Testing Status for EU. Each Zone has its own Development, Staging and Production environment.

What is the best way to manage this with JIRA or JIRA Apps?

[Nic Brough -Adaptavist-]

I've done this with Bamboo deployment projects - they can deploy to many places and report back what version is deployed where.

But if you need to do it in Jira, you've got some options. 

• A terrible way to do it is trying to wedge it into the workflow.  Frankly, the only deployment status I'd even consider doing in workflow is to have a "no more development needed, but not deployed everywhere " status and then a final "deployed everywhere" status.
• A bad but readily understandable way to do it is with a series of "deployment status" fields, maybe a field per region with values like dev/staging/prod ticked off.
• An ok way to do it would be to have a simple checkbox field, one line for each combination of dev/test/live and zone1/zone2/zone3.
• For a bit more power than checkboxes, then sub-tasks might be helpful - simple workflow and only a couple of fields on them, and automatically created by a script

You can probably see that I'm implying all of this is handled on an issue.  A lot of places I've seen work off "deployment issues" - each release has one, which contains and tracks all info related to deployments.  It also works if your stories all lead to deployable items