As a continuation of #593 it’s worth thinking through the implications of a Discussions feature equivalent to GitHub discussions.
Another big upside of allowing for more intentional signal-sorting in the ‘issue tracker’ (I prefer to think of it as a less prescriptive ‘notes tracker’) is that ‘discussion issues’ don’t clog up the TODOs queue.
I always thought it was a massive mistake for GitHub to introduce Discussions as wholly separate post type, distinct from Issues and thus lacking features like backlinking and dividing search in two, even requiring a special conversion to transition from one type to the other.
Following from #593 it can now make sense for every new thread to start out as an untriaged discussion; only what’s deemed an issue is an actual (open) Issue.
Given the entrenchment of ‘Issues’ I don’t have high hopes of persuading anyone, but: I actually favor notes over issues as a more universal term for artifacts of deliberation in a code repo, since issue denotes a rather specific kind of reporting that isn’t the real baseline for the types of threads that’ll be submitted to a repo.
For renaming 'issues', there is #533 Proposal: rename "issues" to "tickets".
I agree. I think distinction between traditional issues and discussions should be on rendering and not on their internal model. I like to go even further and claim that PRs are also just tickets with some extra metadata.
It's pretty hard to draw a line between issues and discussions, actionable tasks and bug reports, proposals and reviewable changes etc. So best way to divide them is to just put everything in same bucket with fully customizable categorizing strategies where each categories will have different rendering styles.
Some might want complete tree-style thread for issues. Some might want "pinned answer" in all tickets. Some might want to make proposals as reviewable item even they don't include any code changes. Some might want two issue tabs for general bug reports and actionable tasks. Modern task management systems don't try to distinguish between "general report", "actionable task" and "ongoing work". Tangled can follow same direction.