Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #28154
Closed
Open
Issue created Apr 18, 2019 by Emanuele Aina@emmhContributor

Port Merge Request Reviews (batch comments) to Core

Problem to solve

Reviewing merge requests currently triggers an email for each comment. This has a few drawbacks:

  • as a reviewer, I often comment on something which is not clear only to find the reason a few lines below, which prompts me to amend/drop my initial comment and I would like to be able to do so without generating useless noise for the MR author
  • as a reviewer, in some cases I have to interrupt a review midway and there's no way to tell the MR author that I haven't actually finished it
  • if there are many small comments, the MR author receives an annoying stream of emails where context is lost soon and the only sensible solution is to ignore their contents, treat them as a single "you have comments" notification and look at the GitLab web UI

This has been nicely solved by the Merge Request Review functionality introduced in GitLab 11.4, see gitlab-org/gitlab-ee#1984

Intended users

  • Documentation writers often receive many small review comments highlighting typos that are not worth an email each
  • Developers need a way to be able to amend their review progressively while they figure out the code flow without annoying the MR author in the process

Further details

gitlab-org/gitlab-ee#1984

Proposal

Can the GitLab EE Review Merge Request functionality be released as part of GitLab CE as well? Thanks! :)

Links / references

  • GitLab EE feature highlight in the GitLab 11.4 release notes: https://about.gitlab.com/2018/10/22/gitlab-11-4-released/#merge-request-reviews
  • Original GitLab EE issue: gitlab-org/gitlab-ee#1984
  • Similar GitLab CE request pre-dating the GitLab EE implementation: gitlab-ce#45225
Edited Jun 03, 2020 by Daniel Gruesso
Assignee
Assign to
Time tracking