You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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!