Suggestion: Add an “Archived Bugs” Tab to Prevent Duplicate Reports
R
Ramratan M
Feedback to Test IO
Dear Test IO Team,
As testers, we would like to kindly request that you consider implementing a system where, if a copied bug is reported (whether intentionally or unintentionally), the payout is automatically set to zero. This approach would help avoid misunderstandings and ensure fairness for both testers and customers.
When we participate in many test cycles for the same customer, it becomes very difficult to manually check all past cycles before submitting a bug. Having such a system in place would allow us to focus on providing valuable and unique findings without the fear of unintended duplicate reports leading to unnecessary actions on our accounts.
We truly want to avoid reporting copied bugs, as they do not add value to the customer. By following this suggestion, it will create a smoother experience for testers and motivate us to confidently report new bugs without hesitation.
Thank you very much for your understanding and consideration.
S
Sablina
Hello, and thank you for your valuable contribution in helping us improve our platform. We truly appreciate you bringing this matter to our attention.
You are absolutely right—tracking duplicate issues can be challenging, especially in recurring cycles with a large number of reported bugs, as well as when duplicates originate from previous cycles. We fully recognize the difficulty this creates for testers.
At the same time, setting the payout for repeated bugs to zero is not a sustainable solution, as it could introduce other complications. Please rest assured that we are actively investigating this matter and working towards a more effective and balanced resolution.
Thank you again for your feedback and for supporting the continuous improvement of our platform.
R
Ramratan M
Dear Test IO Team,
I hope you’re reviewing this feedback.
To help testers avoid submitting duplicate bugs and improve efficiency, I suggest adding an “Archived Bugs” tab where all unresolved bugs (except KB) from previous cycles can be stored. Once a bug is marked as fixed, it should be removed from this tab.
This will make it easier to review past reports quickly and focus on finding new, valuable bugs without the risk of duplicates.
Thank you for considering this suggestion.
R
Ramratan M
Hi Test.io Team,
I am scared to submit bugs now, as I recently received a final reminder email about submitting a copy-paste bug.
The challenge I face is that it’s becoming increasingly difficult to verify whether a bug I find has already been reported in previous cycles, especially when there are 10–15 past test cycles reports to review.
If a bug submitted is the same as one reported earlier, I suggest making its payout zero or whatever test.io rules, instead of taking action against the tester’s account.