Nov 9
Remove the repeated cycles and add a feature, Confirming Previously Known Bugs.
Today, when a customer re-sends a cycle, the customer, for various reasons, cannot fix previously known bugs on time.
Also, the customer does not add previously known bugs to the list of known bugs.
**Also, the customer does not fix the environment itself, but sends this environment again.**
Testers only need to copy their previously known bugs and other people's bugs.
These previously known bugs are marked as 30 percent.
2/3 of the remaining testers are inactive in the cycle and do not add bugs.
**There are no new bugs in this environment. All bugs have already been found.**
I suggest adding a new feature like Confirming Previously Known Bugs.
What for?
In order not to distract other testers because there are no new bugs in this environment.
**It is absurd to invite testers to an environment in which there were no changes, so that these testers would find new bugs that do not exist.**
The repeated cycle serves as a basis for those testers who reported their bugs earlier or copied other people's bugs.
The customer will send previously known bugs to those testers who reported them earlier. Each case will be paid at 30 percent of the severity.
Testers will no longer yell that someone is copying their bugs.
Closed