One issue that our engineering team is tackling with respect to JIRA right now is how to differentiate between tickets that are closed with that verification taking place in a pre-prod environment and which are available in production. With our (relatively) continuous deployment and integration process, we are not using the Version fields in JIRA as much and we can't lookup the generally availability of a ticket based on whether that Version has been released. Any suggestions for shoehorning a (1) closed vs. (2) closed and released to production state differentiation into the default JIRA workflow?
You won't be able to edit the default workflow. You'll need to create a new one. From there you can create new states and add them to your workflow. From there, you will probably want to have "PreProduction", "Ready for Prod" and "Deployed" with the latter being the closing state.
Versions would give you more fine grained detail within those states. Additionally you may want to have your process do an update to the JIRA ticket saying which version was deployed or something of that nature.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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!
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