Jul 5

Add one of the indicators for each cycle: green (covering) or red (specific).

Using the same description for each section (Cart/PDP/Footer..) and the “OOS” section, different team leaders accept the bug differently. For one team leader, this is a bug that corresponds to the section itself (Cart/PDP/Footer..) and is redirected, except for the 'OOS' section For another team leader, this is a bug like 'OOS', because the description of the section (Cart/PDP/Footer..) itself does not cover the bug itself and this bug is rejected. The customer is left without valid bugs ... I suggest adding one of two indicators for each cycle: green (covering) or red (specific): - Green (covering) indicator - when the bug corresponds to the selected section (Cart/PDP/Footer..), the bug meets the quality standards of 'test IO', the bug is valid and the bug is redirected, except for the section 'OOS'; - Red (specific) indicator - when the bug meets the strict description of the section (Cart/PDP/Footer..) itself, including the 'OOS' section; P.S. I think this will be fair for the tester, and it will not allow the team leader to unfairly reject a valid bug if a green (covering) indicator is selected for the cycle!
ClosedClosed