3 ms·
> When you can only tackle so many things there is 0 point in having a bug tracker that will only inflate A public bug tracker isn't just for you. It, arguably
by TeMPOraL 5y ago
> When you can only tackle so many things there is 0 point in having a bug tracker that will only inflate
A public bug tracker isn't just for you. It, arguably, isn't even primarily for you. It's for all your users who experience a problem and want to confirm if someone else also had it, and if there's a known solution.
(It's something that particularly annoys me as a developer. I can fix problems on my own just fine, thank you. But I want to know if my problem is something tied to my configuration, or a known issue of some software that's failing for me - so that I don't waste time looking for the cause in the wrong place. I want the project's issue tracker to help me answer that question quickly - and auto-hiding/archiving/closing stale issues makes this job much harder.)
- feu 5y agoClosing an issue shouldn't prevent anyone from finding it though. At least on GitHub closed issues are still visible in the issue tracker.
- innocenat 5y agoWho search for closed issues when searching if other have the same bug?
- TeMPOraL 5y agoI do, because I realized people close stale issues just because (and then there are bots that do it now too). I'm happy I can still do it, and I worry that one day someone will have a bright idea to "archive" closed issues to where they cannot be easily found.
- NicoJuicy 5y agoI do. Because perhaps it's fixed in a newer version or ...
- kenniskrag 5y agoI think closed issues shouldn't be a problem on the current release. So why search through them?
- TeMPOraL 5y agoBecause - per the pattern of behavior we're discussing in this thread - some developers close old issues, whether they were actually resolved or not, and it's becoming a common practice, particularly with the appearance of bots performing this function automatically. Also, not everyone is using the most recent release.
- spacechild1 5y agoSome issues are not actually bugs but user errors (e.g. because they haven't read the manual). Personally I'm not sure if it's better to close such issues or keep them open with a special label.
- toyg 5y ago> A public bug tracker isn't just for you. It, arguably, isn't even primarily for you. There is a lot of work still to be done on bug-tracking. The eternal attempt to keep users away from bugtrackers has meant that, when they inevitably became public because of FOSS growth, their interfaces did not really work for users. I think it's high time we accepted bug trackers are also forums. There should be a way to mark certain comments as "effective workaround", and surface them at first glance. There should be ways for developers to mark certain comments as "useful info" so that the rest can be filtered. There should be ways to have lengthy discussions attached to the bug but not forced on the developer. There should be incentives to actually solve "historical" bugs first. In short, there should be different ways to look at a bug depending on one's role, without losing anything, without alienating anyone, and accepting the complexity of user-developer relations. But there is very little money in it, I guess.
- TeMPOraL 5y agoThat's a great perspective. I agree with what you wrote here. With that in mind, I believe that properly supporting all the various use cases an issue tracker serves without turning it into another JIRA is a hard UI design task. But at the same time, practices like closing or locking stale bug reports can be seen as UI workarounds. Some people feel their boards are cluttered, so they reach for the only tools available - the close button, the lock button, an autoclosing/autolocking bot. It solves the UI issue for them, at the expense of other groups of board users. This is to say: it's ultimately an UI deficiency on the part of a common issue trackers. Developers should be able to restructure their board as they see fit, but it shouldn't impact other users' ability to utilize the data stored on it. It would be great if major software forges solved this on their end. Perhaps we need a concept of a "stale" issue/thread that's distinct from a "closed" one. A stale issue would be one that's not actively being looked at, but is nevertheless not resolved. The way it would differ from a regular open issue is: - It doesn't sort itself up when somebody posts a comment on it. - Posting on it doesn't notify people who didn't explicitly subscribe to it - all activity on stale issue is grouped under a single, inconspicuous indicator, that can be easily ignored. - Stale issues are always sorted to the bottom or kept on a separate tab, and are trivial to filter in or out during searches. But the tab marker itself stays visible, so that people can find out there are such issues in the first place. - Stale issue can be explicitly promoted to active at the discretion of the developers (or perhaps by community vote). Hopefully this would reduce the need to aggressively close - and especially to lock - older issues.
- Jenk 5y agoStalebot (the popular one on GH) has exemptions which are configurable - branch, author, label, commenter, and probably more. AKA owner/maintainer can do as little as drop a label or even just a reply on an issue and it won't be pruned.