Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,365,059
Community Members
 
Community Events
168
Community Groups

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

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

1 answer

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!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events