Reduce confusion between comments and discussions in merge requests

Problem to solve

Confusion between comments and discussions in merge requests

Further details

I have seen a few reviewers confused about what they should do to give feedback on a merge request. Some comments demanded actions and some discussions were just general observations. The developer can't resolve the comments although the proper commits were done.

We read the documentation about it and I guess we understand it better now, but I feel it could be more intuitive.

Proposal

My suggestion would be two things:

• Make it clearer that there are two options (Comment or Start discussion).
  I don't know... maybe having two separate buttons side by side.
• Have an way to convert a comment to a discussion so we can easily undo the mistake.
  Maybe this is all we need. So when the developers find something that has to be addressed from that comment, they can convert and resolve it.

What does success look like, and how can we measure that?

Success would be to see less comments that should be discussions in merge requests and vice versa

Links / references