When responding to a issue as duplicate, link to the original issue, so we can see when and how it was or wasnt resolved.

That'd require a lot of work for the staff, having to hunt through to find the original issue.

How about this idea instead?
http://forums.invisionpower.com/topic/285816-feature-suggestions/

That would probably about double the amount of time we take marking bug reports, and unfortunately that's not really in our best interests. When there's a visible bug, there are often 30 or more bug reports on the same issue (for instance, the parse error in the bulk mailer in RC2). I'd rather be fixing bugs, than showing members who didn't do a proper search why their bug was marked as a duplicate.

I'll ask the stupid question, how do you know a bug is duplicate if you aren't checking first? Is it possible similar bugs are being marked duplicate when different problems do in fact exist?

Or course the staff reads the whole bug report before marking it as duplicate :P

The developers can normally remember which issues they've fixed :)

[quote name='Μark' date='04 July 2009 - 08:44 AM' timestamp='1246711447' post='1820126']
The developers can normally remember which issues they've fixed :)

Heck, many customers remember a lot of the fixed issues. For example, a particular Bulk Mail bug which was due to the same typo in two places of the bulk mail file.

[quote name='ethan526' date='04 July 2009 - 06:32 AM' timestamp='1246703541' post='1820095']
I'll ask the stupid question, how do you know a bug is duplicate if you aren't checking first? Is it possible similar bugs are being marked duplicate when different problems do in fact exist?


Of course that could happen if the developer doesn't pay attention, but generally we're able to pick up on those sorts of things. We would typically only mark a bug report as a duplicate if we're sure it's a duplicate.