Managing Deployments on different testing enviroments with Jira

[Steffen Döll]

Hi there,

got an interesting question. Our current Team has one product within one jira project. Because of dependencies to other Teams / Business partners we have following setup:

3 Staging Systems to be abtle to test Feature A without any dependy to Feature B on another Staging System which maybe has another Dependencies to our Partners

3 QA Systems (because of 3 Staging Systems)

1 Final QA System

1 Productive

One Story could be deployed to Staging 1 and later to QA System 2, another Story could be deployed to Staging 2 and later to QA System 2 and so on.

How would you label a User Story ticket inside jira to see which story is currently on which server (maybe because a Business Partner or another Team needs a quick view of the feature because of dependecies)?

Would you use labels? Or would you use a custom field? Is there any possibilities to automate maybe a transition from one envirement to another? Anyone has best practices in this case? 

[francis]

You might also go a completely different route and use Bamboo to implement deployments.

Check  here for more information

[Chuck Foster]

@Steffen Döll did you find any solutions?  We have a similar situation with multiple deployments (25+) of the same product/branch.  We are trying to use Jira to better track this.  Right now, we have an awful Excel matrix.