Hacker News new | ask | show | jobs
by mckn1ght 620 days ago
> Some first-class way to differentiate between backlog and todo

That sounds like projects and statuses/milestones. Then the issue list becomes the backlog.

1 comments

Those work from a functional perspective, but don't solve the sticker shock of seeing "issues (852)".
Element is a great example with well over 3,000 open issues, most of which would be far better worked out in Discussions from which the maintainers could raise issues or PRs from whatever the outcome of the conversation was (if any). But they don't have Discussions because...
Yes, I mentioned Discussions in another comment, and that’s the other piece that makes Issues more usable, by siphoning away a lot of the noise that masks the signal. Take away all the me-toos, requests for updates, and discussions of similar phenomena that should be different issues, and Issues would get a lot better. An Issue should be: problem, forensic information, root cause analysis, solution, and record of work.