Jul 14
Don't Archive Cycles Before Disputes In That Cycle Are Resolved
Test cycles are
sometimes archived before pending disputes are resolved. This locks in
rejections and prevents testers from getting fair credit, even if they
later win the dispute.This
has happened to me personally. I submitted a bug, the cycle was
archived before my dispute was resolved, and even after winning the
dispute, my bug status remained rejected. This permanently hurt my
approval rate, even though I was proven right.Testers
lose motivation when they know a dispute win won't restore their
approval rate. Approval rates are permanently damaged, and testers are
penalized for rejections later proven wrong.Test
cycles should be kept open or "on hold" until all disputes are
resolved. If the tester wins, the bug status should be updated
automatically.A fairer system would lead to better bug reports, higher tester trust, and stronger retention.
Closed
Hello! Thank you very much for taking the time to share your feedback. We understand why this situation can be confusing, and we appreciate you bringing it to our attention. We know that, in some cases, it may seem as though a tester loses ranking or receives a lower approval rate even after a dispute has been accepted. However, it's important to note that the dispute review and the Team Leader's evaluation are two separate processes, each serving a different purpose. A Dispute Manager reviews a certain bug report and determines whether the dispute should be accepted based on the specific circumstances of that report. A Team Leader, on the other hand, evaluates the bug within the broader context of the testing cycle, taking into account the customer's expectations, product knowledge, and project-specific requirements. Since Team Leaders often work with the same customer across multiple test cycles, they are in the best position to assess bugs according to that customer's standards. As a result, a Dispute Manager's decision may affect the tester's bonus, but it does not change the Team Leader's evaluation or the bug's final status. Once a test cycle has been sent to the customer, the bug status can no longer be modified. As testers gain more experience, they usually encounter fewer situations that require disputes, as they become more familiar with customer expectations and submit fewer borderline or controversial bugs. For this reason, dispute outcomes generally have only a limited impact on a tester's overall statistics over time. We hope this helps clarify how the process works. Thank you again for your feedback and for helping us improve the testing experience for everyone.