Resolvability of discussions in epics and issues
Description
Original description
Problem to solve
Merge requests have really nice discussion management tools (go to next discussion, list # of open discussions). For whatever reason, issues do not have these same tools so they become much harder to follow as they grow over time.
We want to maintain a transparent way of working, but the limited tools in issues to manage discussions is causing a lack of transparency due to confusion or density of information that is difficult to get up to speed on.
Target audience
This would impact all users of Issues
Further details
See https://gitlab.com/gitlab-org/gitlab-ee/issues/7380 for a example of an issue that is busting at the seams with discussion threads and is really hard to keep up with. An ability to jump between discussion open threads, see how many are open would be so helpful.
Proposal
Bring in the same discussion management code from MRs to issues. It's better to have one codebase for discussion management that can apply both to MRs and issues than getting them in sync, because if we just get them in sync they will start to drift again.
What does success look like, and how can we measure that?
Much easier to understand long-running or complex issues
Links / references
cc @victorwu