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
Hi @Khawaja Adeel,
If you make the QA step an integrated part of your workflow, there is no reason to create duplicate tickets. You just update the ticket status to QA (you may even use a post function or an automation to update the assignee automatically as part of the status update) and make sure your QA people can either approve or reject the issue, which moves it in either the next status or back to the dev team.
Hope this helps!