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."
closed
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."
Tetiana Yezerska
closed
Thank you for your suggestion. After reviewing our records, it appears that this suggestion was made quite some time ago and may have already been addressed or implemented through other processes.
If you believe this suggestion is still valuable and needed, please feel free to create a new suggestion so that we can review it with fresh eyes.
In the meantime, I close this suggestion as it is considered to be old and may not be as relevant anymore.
Thank you for understanding and for your contribution to improving our processes.
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.