Improve experience of multiple reviewers at the same time in the same Merge Request

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Release notes

Reviewers should have a smooth experience when reviewing one MR even if multiple reviews are happening at the same time.

This issue is aimed at starting a discussion and gather proposals and thoughts.

Problem to solve

When you have one Merge Request with multiple disciplines being reviewed (eg: Backend, Frontend, Database), the comments being left can be hard to sift through for each of the reviewers.

Intended users

• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Devon (DevOps Engineer)
• Rachel (Release Manager)
• Alex (Security Operations Engineer)
• Simone (Software Engineer in Test)

User experience goal

To be discussed, open to proposals.

Proposal

Open to proposals

Further details

This issue arose during the Iteration Office Hours of Sept 23rd 2020.

Documentation

Availability & Testing

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

What is the type of buyer?

Is this a cross-stage feature?

Links / references