Finding new inline comments is quite hard

Summary

Currently finding new inline comments in merge requests with many unresolved discussions is quite difficult.

Steps to reproduce

Imagine that you are reviewing an MR. You sit down, read the patch, and spot a numerous issues which you relate to the author with several inline comments. You eventually submit your review.

It turns out that the issues you point out are a bit thorny and require quite some discussion: The author replies, then you reply, and this cycle continues for some dozens of comments. However, as the thread grows it becomes harder and harder to identify which comments are new: every iteration you are forced to traverse the entirety of each discussion to look for new replies.

Example Project

See, for instance, the discussion on https://gitlab.haskell.org/ghc/ghc/merge_requests/74.

What is the current bug behavior?

Comments are shown in threaded form in the Discussion and Changes tabs; there is no way to get a convenient chronological view of comments.

What is the expected correct behavior?

It's unclear but the status quo is quite painful during larger reviews.

Phabricator had an interesting approach to this: discussion comments would be shown in chronological order at the top of the code review and the inline comments would be shown as threads in the inline view. See, for instance, https://phabricator.haskell.org/D4777.

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.)

Results of GitLab environment info

Version 11.5