Update the "Known Bugs" column constantly, when the report receives the status "Rejected - this bug is not relevant to the customer and will not be fixed."
under review
ted
During testing, the customer first rejected the report with the status "Rejected - this bug is not relevant to the customer and will not be fixed."
The second time, another tester found the same bug that was previously rejected by the customer, but the tester itself did not participate in the first cycle.
Since the bug itself is not displayed in the "Known Bugs" column.
Thus, a repeated bug will be rejected by the team leader.
A proposal, so as not to take time from team leaders, to update the "Known Bugs" column constantly when the report receives the status "Rejected - this bug is not relevant to the customer and will not be fixed."
Evgeniya Graich
under review
ted
1.The proposal describes one of the scenarios.
2.There is another scenario when the same tester duplicates a bug that was rejected by the customer.
Evgeniya Graich
ted: Thank you for your suggestion. Would you not mind that the list of known bugs will be increased then?
ted
Evgeniya Graich:
No, I don’t mind.
I will receive full payment in this case.