Hm. Why *do* issue trackers automatically close issues marked as duplicate? Wouldn't it make more sense to keep them open and visually group them together, and auto-close them once the duplicant issue is resolved, so that it gives you an idea of how many people have individually reported the same issue and no context/variations are lost?
not sure if this is rhetorical or not?
@joepie91 because a lot of people will find one of those issues, and marking a single canonical place for all discussion of a particular issue is really useful.
not that there couldn't be better UI around that, it just seems like "close all but one of the issues, put links to them in a single canonical issue" has a pretty good balance of ease of use/low friction and centralizing discussion.
@alive In practice a lot of 'duplicates' are not *exact* duplicates but rather different issues caused by the same underlying cause, and in that context this model unfortunately doesn't really work either.
@joepie91 yeah, but that strikes me as a problem with the resources/philosophy that the maintainers have, which i think is something that's hard to move the needle on by tweaking software.
@alive To be clear, I'm not saying that those shouldn't have been marked as duplicates - from a fixing perspective it makes sense to do so, since they have a shared cause. Just that the issues are not *identical*. That's definitely a case that can be accommodated in the software, one way or another.
