How to handle workflows and statuses for tickets moving through different environments?

Dharmesh Barot

Hi,

We are on Jira Cloud. Various teams use slight variations of workflows based on project types.

All tickets go from Backlog to QA (Test environment). Usually in the same sprint.

From QA onwards variations happen.

For example, 

Project A - may have a BETA environment for UAT

Project B - may have BETA and a Pre-prod environment for another round of UAT

Project C - may have an integration environment to test end to end, BETA, and a pre-Prod environment

 

A ticket is resolved when it moves to Done, so potentially it could go

Backlog > QA > Integration > BETA > Pre-prod > Done

 

Teams would like to report on current sprint when tickets pass QA, but they are open because they have not gone through other environments, which may happen in Sprint 2 or Sprint 5.

 

What is your recommendation on the setup of workflows and board, so we can see sprint progress on tickets accurately?

 

Looking forward to an informative discussion.

 

Best,

 

Dharmesh

John Funk

Hi Dharmesh,

We have actually done something similar using a single workflow. We have all of the statuses in the workflow.

We then have a custom field called Dev Needs. That fields is a checkboxes type field where you could put in the values of Integration, Beta, and Pre-Prod. So a user could check one or none of those values.

Then the workflow has a transition from QA to Integration with a condition that the Dev Needs field must have the Integration box check. 

Same for going from QA to Beta. 

And same for going from QA to Pre-Prod

Then each of those would have a transition to Done. 

You just use transitions in the combination needed for the workflow needed based on the values checked in the Dev Needs field (or whatever you want to call the field). 

That way, there is one issue type for us and one workflow that is flexible.