Thomas Klein on Nostr: Wow, thanks for the degree of transparency. On the other hand though, my day job QA ...
Wow, thanks for the degree of transparency. On the other hand though, my day job QA manager can't but shiver on these 27.1% of duplicates.
Duplicates usually mean "wasted QA / DEV resources" 🙂 - unless these duplicates are identified as such as early as possible in the bug lifecycle.
Do you do any kind of QA / triage on newly submitted bugs to check dupes right away or leave that to the later stages (such as devs) to decide whether it's a duplicate?
And then: Would it help to educate bug submitters to check for known issues upfront?
Just curious, because 27% of 484 bugs means 130 duplicates with each of them being sighted, checked, handled...
Anyway: Good job! Rock on!
Duplicates usually mean "wasted QA / DEV resources" 🙂 - unless these duplicates are identified as such as early as possible in the bug lifecycle.
Do you do any kind of QA / triage on newly submitted bugs to check dupes right away or leave that to the later stages (such as devs) to decide whether it's a duplicate?
And then: Would it help to educate bug submitters to check for known issues upfront?
Just curious, because 27% of 484 bugs means 130 duplicates with each of them being sighted, checked, handled...
Anyway: Good job! Rock on!