Tips on disputing a bug - Yolanda Solo

Author: Yolanda Solo


As a tester you have the option to dispute a limited number of bugs each month, but this is a feature that should be used wisely and sparingly. Testers can only dispute a limited number of bugs per month and if a dispute is rejected, the decision is final. We have outlined some tips that will help you determine if you should file a dispute and how to do so appropriately.

Many rejections could be avoided by spending more time submitting a bug properly at the first stage. Read the list below and make sure you followed the correct procedure that ensures bugs are valid before you submit the dispute.

  • Check the “Scope & Instructions” to make sure that the bug is within the scope of the test cycles.
  • Check a Known Bugs List (if applicable) and previously submitted bugs list for duplicates. The most common reason for bugs getting rejected is that they are a duplicate. The similarities may not be obvious from the title and will be found in the description or test case result.
  • Check the discussion thread to see if the issue you found has been discussed and clarified. You might find that the project manager has already told testers in the discussion thread that some issues are not within scope.
  • Check your rejected bug thoroughly – did you provide a clear, concise description of the bug that will allow the client to reproduce it and illustrate it with evidence including screenshots and/or video captures? If not, you may now understand why your your report was rejected. Thus, make sure you add all the necessary information and supporting evidence when you submit your dispute.

Reasons for disputing a bug

Having checked that you bug submission meets the necessary criteria you may want to dispute a bug rejection for the following reasons:

  • You did not provide enough information the first time
    If the information you gave in the initial test case result was not clear enough, you can clarify any information in the dispute if you feel it will help the customer understand the issue better.
  • You have additional evidence
    If the customer was unable to reproduce the bug you can provide screen shots and screen captures showing the bug.
  • Your bug was rejected for duplication and want to explain why yours is different
    A bug may be similar to others and therefore get rejected by mistake. Explain why your bug is unique to ensure that the dispute is handled correctly.


  • All disputes, tester messenger discussions, and discussion thread discussions are monitored by uTest and the customer. Therefore, be professional in your communication at all times.
  • Any disputes must be submitted using the dispute feature. Never ask customers not to reject your bug as 'works as designed' as this may result in the suspension of your account.


How to dispute a bug rejection

  • Explain why you are disputing the rejected bug
    You have a limited amount of room to write your explanation so make sure it is clear and concise. Explain why you are disputing the rejected bug and address the reason it was rejected e.g. if it was rejected as a duplicate bug, explain the differences between your bug and similar bugs.
  • Add supporting material
    If you feel the customer did not fully understand the bug it is essential you provide supporting evidence. Screenshots are good, video captures are better so that customers can see step-by-step what you are trying to explain. You can upload the screenshots and video captures directly to the uTest Platform.