GitLab MR tasks
GitLab MR tasks
Code reviews are also work. Create a task for every GitLab Merge Request and stay on top of your code reviews.
By
DevRev

GitLab MR tasks

Code reviews are also work. Create a task for every GitLab Merge Request and stay on top of your code reviews.

Overview

image

Code reviews can be time consuming — we may not always account for this in planning which may lead to poor estimates and delays. Make sure your code reviews are tracked as tasks, so you can stay on top of them.

Create tasks when you are added as a reviewer on an MR. When you enable this automation, we’ll create a task corresponding to this code review. This task is embedded in the related issue, and can also be tracked under My Tasks.

How it works

To use this automation, you'll need to connect your GitLab with DevRev so we can listen to MR events. When you install this flow, we'll walk you through a few simple steps to connect and setup your reminders. You can find more on the supported connection methods here.

Features

Your code reviews are also work and need to be accounted for. Use this automation to create a task for every code review, and stay on top of your GitLab MR reviews.

Automatic MR tasks

When a merge request is requested or reopened, a DevRev task is created for you. In order for this automation to be triggerred, you'll need to link your Merge Requests to DevRev issues. If your MR is removed, merged or closed, then the Task gets deleted. However, if you submit your MR review, then the task is closed.

Frequently asked questions

What are the prerequisites for creating MR tasks?You'll need to connect your GitLab identity with DevRev identity, so we can attribute the tasks to your DevRev user identity. You can link your GitLab identity by going to DevOrg Settings → Account → External Identities → Link GitLab Account.