Hacker News new | ask | show | jobs
by mikeocool 620 days ago
Please god add a “closed - duplicate,” “closed - won’t fix,”and maybe “our bot closed this because no one commented on it for 6 weeks” status.

Nothing is more frustrating than finding an issue that exactly describes what your are experiencing marked “closed,” scrolling through months of comments only to find that the issue still exists and it’s been closed for one of these reasons.
3 comments
mckn1ght 620 days ago
Labels have been able to do this for years, why are they not a sufficient solution?

And even if they elevated these to first class items, nothing is stopping maintainers from still closing them or letting them be closed without the issue having been actually fixed.

link
nikeee 620 days ago
Because a label does not contain a reference to the issue that was duplicated. You still have to scroll through the issue's timeline to find it.
link
mynameisvlad 620 days ago
Neither do the statuses as suggested.

Your suggestion is to add a field that will only be used in a single status, which goes against the simplicity of GH Issues (which this update already makes contentious enough, looking at the comments here).

Also, realistically, there will be a mention of the issue in the final ticket, so is scrolling down to the bottom of the issue that hard? You're making it seem like it'd be buried in the middle of the timeline and while that can happen, I don't see that being anything but an edge case. Most tickets won't be referenced after they're closed as dupes.

link
bluGill 620 days ago
This tension is why issue systems become too complex. The ask is reasonable, but implementing it makes the issue system more complex until all the simple asks make the system collapse under the weight of it...
link
mckn1ght 620 days ago
Absolutely. The sum total of reasonable requests can be an unreasonable system. It’s a paradox just like Gabriel’s horn: finite volume, infinite surface area.

Reading through this comment section makes me see exactly how something simple like a GitHub issue becomes a JIRA issue.

This is why I like simple, opinionated solutions. This kind of discussion becomes superfluous.

link
TheBruceHimself 619 days ago
I'm shocked they haven't added this. Especially with so many projects using bots to close issues just because of inactivty (annoyingly when the inactivity is on the side of the develops, not the person raising the issue).

I'd also say the fixed issues should immediately tell you what PR fixed the issue if possible. It frustrates me to no end when someone says the issue is fixed and they are 5 to 6 referenced PRs in the issue and it's unclear which actually fixes the issue or just mentions the issue in a comment for some reason.

link
JamesSwift 620 days ago
Stalebot is a scourge on society. Half joking. Mostly not though.
link