Dispute FAQs

We have compiled some frequently asked questions’ regarding situations encountered after a bug has been rejected and a tester desires to dispute it. Remember, you may only use the dispute feature to dispute a bug - do not use the Real-Time Chat or Tester Messenger to dispute. If my bug gets rejected, how do I find out the reason?

  • When a bug is rejected, an email containing the rejection details is automatically sent to the tester. Please sign in to the uTest platform to follow up with bug disputes as needed.

Can I dispute a bug for any reason?

  • Testers may dispute rejected bugs, so long as you are fair and communicate professionally with customers. Note: All testers have a limited number of disputes per month, so please use them appropriately. If you decide to dispute the bug, be sure to provide further evidence, such as screenshots and video captures and upload these directly to the uTest Platform (you can upload new attachments after you dispute the bug by clicking on the "Edit" button of the report). This will increase the likelihood of your dispute being accepted. More information about disputing a rejected bug can be found here.

Can I upload new attachments when I dispute a rejected bug?

  • Yes. In fact, we recommend that you always provide further evidence upon disputing a rejected bug. This could come in the form of new screenshots or even a video capture. Please note that you can only edit your bug report and upload new attachments after you have disputed your report.

I cannot dispute any more bugs. Why?

  • All testers have a limited number of disputes per month. Each tester has 2 disputes, plus 10% of his/her approved bug count in a 30-day window. If a tester's dispute is approved, the dispute approved bug will not count towards the dispute limit.

What if my dispute gets rejected but I still disagree?

  • If your dispute is rejected, there is no further action you can take to reverse the customer's decision. In order to avoid this, please make sure that your bug report is clear, concise and within scope. This is by far the best way to avoid bug rejections and disputes.

Dispute a Rejected Bug:

 dispute