3 ms·
Right. In a very different context, I implemented something a lot like this for a game's bug tracker, using assignments. Ask the player to clarify something, a
by abathur 6y ago
Right. In a very different context, I implemented something a lot like this for a game's bug tracker, using assignments.
Ask the player to clarify something, assign the bug to feedback. If no one ever comments to save it, it'll get nudged a few times before it's automatically dismissed.
It was a godsend, because it got those issues out of the triage queue and didn't return them until they were actionable again.
- dathinab 6y agoThe problem is it had become not uncommon that any kind of stale issues get automatically closed not just such which "need feedback". I.e. you make a bug report, it get's verified but is low priority. Because of higher priority issues the maintainers do not yet work on it. The issues becomes stale and now the maintainers will never work on it unless you always prevent stall or reopen a new issue. And sometimes there are issues which can not be resolved but still are issues (e.g. (for now) unsolvable bug) IMHO such issue should stay open even if there will not be any work/improvement on them for maybe years.
- abathur 6y agoYes, this is why I'm describing a design that focuses on just what needs feedback.