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?
@joepie91 I think merging would make more sense as you don't loose context, but also don't have to deal with multiple issues where context is spread across them.
@Vampire I feel like that's better solved with something like an inline visual expansion of 'related' (ie. duplicate) issues - especially because "duplicate" is often a fuzzy definition, with them not being *exact* duplicates, just different issues with a shared cause
@joepie91 Hmh not sure how to visualise how that would look like.
@joepie91 I think I get what you mean and it might be better than merging, though I still have some unspecific UI/UX concerns.
Then I said merging, I meant it like old forums dealt with duplicate topics, but that usually disrupted the flow as you suddenly have a bunch of comments which refer to a different idea.
Hmh
Yeah, I dunno.