4 ms·
As a user, I find such a “cleanup” problematic if it means closing the issue. If the issue still exists in the product, it should remain open, for documentation
by layer8 3y ago
As a user, I find such a “cleanup” problematic if it means closing the issue. If the issue still exists in the product, it should remain open, for documentation, and so that users running into it can easily find it and add to it. I find it more honest if a project acknowledges that the issue exists by leaving it open.
As a developer, I’d rather use a filter to hide older non-critical issues, if I’m bothered about seeing the amount of issues.
- eikenberry 3y agoClosed doesn't have to mean resolved and the tickets would still be available either way. Closed is IMO ideal for these tickets as ultimately it means that they aren't being looked at.
- eternityforest 3y agoBut they should be looked at. They aren't because we don't have infinite time every day to look at issues. If those issues are still a problem nobody will find them, they'll make new issues and lose all the previous history, unless the UI is designed to support automatically suggesting reopening an old issue instead.
- jrmg 3y agoIt's not necessarily true that they 'should' be looked at. Most old projects that follow the 'never close without verification' philosophy end up, eventually, with a majority of open issues not actually reflecting the current state of the project. A middle-ground might be to leave open the issues with recent activity, with the idea being that at least the ones that are affecting people the most are not swept under the rug.
- joepie91_ 3y ago> Most old projects that follow the 'never close without verification' philosophy end up, eventually, with a majority of open issues not actually reflecting the current state of the project. There's a crucial question here that I find not enough people ask themselves: does that actually matter? And if yes, why? What, specifically, is the material problem caused by this situation? It often feels like people are just chasing 'inbox zero', under the assumption that "0 open issues == good", without any actual material problem being solved in the process. (Github probably isn't helping here, with their undeservedly prominent placement of the open issue count driving this sort of behaviour...)
- deleted 3y ago[deleted]
- Denvercoder9 3y agoLots of projects on GitHub (not sure about lodash) automatically lock closed issues so you can't comment on it anymore. That closes an avenue for those that are impacted by the issue to discuss fixes, workarounds and alternatives.
- layer8 3y agoClosed implies that a decision has been made that the issue is somehow not worthy of consideration anymore. That’s what bugs me as a user. Whether any given ticket is being looked at can change over time. Closing it is a way to drastically reduce the likelihood that it is being looked at. As a user, I see no good reason why that should be done, in particular when it is applied across the board without considering the individual issue.
- ncruces 3y agoClosing means it's not worth of consideration at this time, it can always be reopened. As a user you obviously see no good reason for that. As maintainers having more bugs open than will ever be worked on (e.g. because no one will put up the legwork), serves no good purpose. PS: individually considering each of 100s of issues takes time and mind share, that can better be invested elsewhere.
- Falkon1313 3y agoClosed does mean resolved. One way or another. If it's not resolved, it's still open. If the ticket was improperly marked closed, that just means someone else has to create a new ticket for the unresolved issue.
- gochi 3y agoClosed doesn't mean resolved, it means closed. Closing issues just shifts them to another tab, doesn't remove them entirely. What you propose, a filter to hide these, is exactly what has been done just through the official open/closed filters.
- layer8 3y agoThis is not accurate. When searching for issues, users won’t find closed issues by default. When issues are linked, closed issues are rendered differently (struck through). You can’t comment on them anymore without reopening them, and reopening them is often discouraged or not enabled at all. It is a drastically different state.
- eddythompson80 3y agomost of that is not really true. where are closed issues rendered struck through? It's up to the repo to lock closed issues or not, and it doesn't appear this repo did that.
- rimunroe 3y agoWait what? Since when can’t you respond on a closed issue without reopening it? I’ve partaken in lengthy discussions on closed issues without them reopening. Obviously you can’t reply to locked issues of course, but that’s a separate thing.
- rezonant 3y agoEither you are thinking of other project management tools or assuming that some of the "stale issue locking" and automated issue management tools that some larger projects use are default. On GitHub, it is true that the Issues search shows only open issues by default, but I think users are quite aware that they may need to search for closed issues, especially since it's unlikely they are on the absolute latest version of a package, especially when debugging problems in production. Additionally, some projects close issues once the mainline has addressed them even if the fix isn't in a released version. GitHub does not render closed issues as struck through, and it does not by default lock conversations on closed issues. EDIT: I am not taking a side on whether or not it's a good idea to do this sort of "bankruptcy" mass close.