Holding Area for Jira Tickets

[Mitchell Sharoff]

Hi,

We have a process where once developers have finished coding and fixing a defect they have to submit it to their manager for a code review.  Once the code review is done, the manager moves the tickets over to QA testers for verification.

The issue we have is that this process is done before the actual code drop with the fixes in them.  There is no way to "hold" or let the the QA testers know when the code has actually been deployed.  This causes a lot of unecessary work done by QA testers who started testing items where the code has not been dropped yet.

Does anyone know of a setup where we could have a process where once the manager has approved the code, she can assign the QA tester to the ticket but put it in some sort of holding area where she can then release them all after the code has dropped.

Thanks for any suggestions!

[josh]

Hi Mitchell,

You would have to build this into your workflows. For example, I have a workflow that has five key statuses: Open --> In Progress --> Validation Backlog --> Validation --> Closed. The purpose of Validation Backlog is to "hold" issues that have completed development and are awaiting QA.

-Josh

[Mitchell Sharoff]

Hi Josh,

Thanks.  When the tickets are in Validation Backlog, who are they assigned to?

[Sam Hall]

Here are a few options of different ways I have seen similar scenarios dealt with:

1. Use an "Awaiting Deployment"-type status in the workflow. Issues in this status are assigned to the person (or team) responsible for deploying code into a testing environment. Once they are deployed they get allocated to the manager who is then responsible for allocating to QA testers.

2. Use the "Fix Version" field to show what version of code the issue is fixed in. Make sure QA testers know which version is deployed in a particular testing environment today (write in on whiteboard, a Confluence page or even use 'environment' issue types in JIRA to track). This means the QA testers know to only test fixes relevant to the current deployed version. Give them a board or filter to help them identify these issues.

3. Use a 'Deployed In' custom field, which has a check box for each environment that the code could be deployed in. Keep this up to date so that everyone knows where a particular fix is on route to production.