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
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?
Reopening the original ticket is better way to track all the efforts, total actual costs etc.
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.