Missed Team ’24? Catch up on announcements here.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

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

Khawaja Adeel
Khawaja Adeel August 29, 2022

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

Answer
Watch
Like Be the first to like this
377 views

1 answer

0 votes
Walter Buggenhout
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
August 30, 2022

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!

View More Comments
Khawaja Adeel
Khawaja Adeel August 30, 2022

ok

Like
Reply

Suggest an answer

Log in or Sign up to answer
Portfolio for Jira
Advanced planning
TAGS
AUG Leaders

Atlassian Community Events

    See all events