Got to love PM/other dev ignoring to review an open PR for weeks, now PM creates a copy of those PRs and I get to smack him with the "is this a duplicate?" knowing damn well it is and he should have gotten off his high horse and looked at the damn PRs.

There is a bug in prod where saves weren't properly propagating, so these PRs need to be merged ;P

Hmm... Had similar experience fairly recently. A long time ago I had encountered an issue, but instead of blindly reporting it I checked the bugtracker, sifting through the terribly written legacy reports, && found that _very_ old report about the bug, so started ignoring it since 'already reported'.

Recently a New Hire found the issue. The Lead Tester ponced like a cheetah that saw a prey.

LT: "That's a bug - report it."

NH: 'Done, ready for review.'

LT: 'Looks good, well done.'

/* Mandatory pat on the back. There's a lot of that in the current team... */

Me: * Leaves a comment *

'This issue duplicates the already reported $report.'

Felt good. Was also fun to watch them scrambling in the chat.

LT: "Damn, looks like we've reported a duplicate."

Yeah LT should have taken him through the reports and shown him how to look it up and such

Yup. But apart from learning about how to look up old bugs so that you don't duplicate, their way of working is just bad. For some reason there's a lot of 'leaders' yet they create reports of so low, generic quality. I may have been doing that solely up to somewhere around 1 year. Even then I've picked up a lot of good practices, which keep evolving.