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
Community Members
Community Events
Community Groups

What is the best practice when a ticket fails QA: reopen the ticket or create a new one?

What if a ticket failed QA-testing:


In the past, we always created a new ticket (linked with the original ticket) because it was easier to follow up and quickly see what needed to be done (fi. fix a specifiek button).


But now we are trying to figure out the total actual costs of our new features and it is more easier when all work time is logged in 1 single ticket. (sub-tickets can be used to track issues)


What do most organizations do? Create a new ticket or reopen the original ticket?

2 answers

2 accepted

0 votes
Answer accepted
Deepak Rai Community Leader Sep 14, 2022

Reopening the original ticket is better way to track all the efforts, total actual costs etc.

0 votes
Answer accepted

Hi @Dirk Vansina ,

that point is one of the most discussed in the community! From my perspective, the best way is to have a workflow that, in case of failure in QA, ticket can be moved back to dev in order to fix the issue. Pro of that approach is that history of ticket, including comments, branch/code/commit and all other information are available to developer.


@Fabio Racobaldo _Herzum_ For reopening tickets: would it be best to add a new status 'reopend for development' (which is equal in the flow as the status 'selected for development')? Or try to reuse the previous statusses of much as possible? What do most organizations do?

Personally, I reuse the existing status

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

5,041 views 18 32
Read article

Atlassian Community Events