I’m wondering about the best way to handle QA feedback in Jira for unreleased features. Should testers create new bugs or just comment on the original issue?
I can see pros and cons for both:
Commenting on the original issue:
Keeps all info in one place
Better for time tracking accuracy
Creating a new bug:
Easier to track the number of issues found
Might help measure developer performance
What do you guys think? Is there a way to get the benefits of both approaches? Or is one clearly better than the other?
I’m really curious to hear how other teams handle this. Thanks in advance for any advice!
Having worked on several agile teams, I’ve found a hybrid approach to be most effective. We create new bugs for significant issues that require substantial work or affect multiple components. For minor tweaks or quick fixes, we use comments on the original issue. This balance allows for accurate tracking of major problems while avoiding excessive ticket creation for small items.
It’s crucial to establish clear guidelines with your team on what constitutes a new bug versus a comment. Regular review of this process ensures it remains effective as your project evolves. Additionally, utilizing Jira’s linking feature helps maintain relationships between related issues, providing a comprehensive view of feature development and testing history.
hey there! in my experience, it’s best to create new bugs. it’s easier to track and measure progress that way. plus, you can always link the new bug to the original issue for context. just my two cents, but it’s worked well for our team. hope that helps!
As a QA lead for the past 5 years, I’ve grappled with this exact dilemma. Our team ultimately settled on creating new bugs for most QA feedback, but with a twist. We use a custom field to categorize the severity of the issue - critical, major, or minor. This approach gives us the best of both worlds.
For critical and major issues, having separate tickets allows for better tracking, assignment, and resolution. It’s especially useful when dealing with complex features or when multiple developers are involved.
For minor issues, we still create separate bugs, but we have an automated process that links them to the original feature ticket. This keeps our backlog clean while maintaining traceability.
One unexpected benefit we’ve found is that this method provides valuable data for improving our development process. We can analyze patterns in the types of bugs caught during QA, which has led to targeted training and process improvements.
Ultimately, the key is consistency and clear communication within the team. Whatever approach you choose, make sure everyone understands and follows it consistently.