How to avoid duplication of tickets while assigning to QA or assigning back to team after QA

[Khawaja Adeel]

How to avoid duplication of tickets while assigning to QA or assigning back to team after QA

[Walter Buggenhout]

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!

[Khawaja Adeel]

ok