Holding Area for Jira Tickets

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!

2 comments

Josh Steckler Community Champion May 04, 2017

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

Hi Josh,

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

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.

 

Comment

Log in or Sign up to comment
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Bridget Sauer
Published yesterday in Marketplace Apps

Calling all developers––You're invited to Atlas Camp 2018

 Atlas Camp   is our developer event which will take place in Barcelona, Spain  from the 6th -7th of   September . This is a great opportunity to meet other developers and get n...

42 views 0 3
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you