Every bug you report needs to pass a review process. At any time, the bug report will reflect the current state of your bug.
- After you file a bug, the report will have the status Submitted. Now the team leader has to review the bug.
- If the team leader has further questions, the bug status will change to Manager Question. Once in request state, you have 18 hours to edit the bug and add requested information.
- If a request was sent to you and you edited the bug, the status will revert to Submitted. The team leader will once again review your bug and make a decision.
- If your bug is not legitimate, not well-documented, or if you didn’t respond to a request within 18 hours, the report get Manager rejected. If you are convinced the team leader decision was wrong, you can use the Bug Dispute.
- In all other cases, the team leader will approve the bug and its status will change to Manager approved. It’s now the customer’s turn to review your bug report.
- Customers can also ask for more information. The status will then be Customer Question.
- When the customer accepts the bug, its status will change to Accepted and you get paid for it.
- When the customer rejected the bug, its status will change to Rejected. You can dispute such decisions as well.
- Submitted: The submitted bug is awaiting review by the team leader.
- Manager Question: The team leader has sent a request for more information within the last 18 hours. The request is still pending.
- Manager approved: The bug has passed the team leader review and is now visible to the customer. A final decision will be made by the customer within 10 days after the test ends.
- Manager rejected: The team leader rejected the bug with a specific reason. The decision can be disputed.
- Accepted: The customer reviewed the bug and accepted it. The tester is paid.
- Rejected: The customer reviewed the bug and rejected it. The decision can be disputed.
Bonuses for customer rejected bugs
If a customer rejects your bug with one of the following reasons, you automatically get a bonus:
- Rejected – this bug is not relevant to the customer and will not be fixed.
- Rejected – this device is not relevant to the customer and, therefore, the bug will not be fixed.
- Rejected – this is a legit bug but already known.
- Rejected – this bug only occurs in the testing environment and not in the live system.
A dispute cannot be submitted in these cases.
We will introduce new bug statuses in the future to better differentiate between the different steps.