3 ms·
An automatic clean up bot could help but is usually not thought through (as numbers examples in this thread describe). There are two common cases where some au
by gumby 6y ago
An automatic clean up bot could help but is usually not thought through (as numbers examples in this thread describe).
There are two common cases where some automation can help:
- User reports bug, dev explains that "it's not a bug, here's why, xxx" (or otherwise provides a satisfactory response) and user, even if satisfied, fails to return to close bug. So instead devs have to remember to close the bug which they usually do immediately after responding, which comes off as abrupt, even though it's not meant that way.
- User reports bug, dev responds with request for more info ("I can't duplicate; could you provide a better test case?"), user never responds.
In both cases it's OK to time out these old reports (which are essentially clutter). You could provide a way for the dev to flag this as one not to be auto-cleaned up.
Another improvement, while I'm at it: provide a Godbolt-like way to submit a test case that can be outrun (i.e. a CI case). Then the bug could be auto-closed if it's in the current release but already fixed in the dev sources. Not all bugs or applications could take advantage of this of course.