doc/tutorials/merge_requests/homepage.md
{{< details >}}
{{< /details >}}
{{< history >}}
merge_request_dashboard. Disabled by default.merge_request_dashboard enabled on GitLab.com in GitLab 17.9.mr_dashboard_list_type_toggle enabled on GitLab.com in GitLab 18.1.merge_request_dashboard enabled by default in GitLab 18.2.{{< /history >}}
[!flag] The availability of this feature is controlled by a feature flag. For more information, see the history.
This tutorial introduces you to the new user interface for managing merge requests.
Whether you're an author awaiting review, or a reviewer providing feedback, this page helps you track your work. It sorts your work into clear categories to help you:
To see your merge request homepage on GitLab.com, either:
It's organized into three tabs, to help you focus on what needs your attention right now, while still giving you access to other recent work:
GitLab shows the total number of Active merge requests in the upper-right corner on all pages. For example, this user has:
Each table row groups related information about a merge request together into columns:
+ / -).0 of 3.In the upper right, select Display preferences ({{< icon name="preferences" >}}) to sort your merge requests by:
{{< tabs >}}
{{< tab title="Workflow view" >}}
In the Workflow view, the Active tab sorts merge requests in this order:
Merge requests in these states are excluded from the Active count:
{{< /tab >}}
{{< tab title="Role view" >}}
In the Role view, the Active tab sorts merge requests in this order:
{{< /tab >}}
{{< /tabs >}}
The Role view groups merge requests you are an assignee or reviewer for:
Merge requests in the Active lists count toward the total shown in the left sidebar.
The Workflow view groups merge requests by where they are in the review process. This view helps you understand what action to take next:
%%{init: { "fontFamily": "GitLab Sans" }}%%
flowchart LR
accTitle: Understand the Workflow view
accDescr: Diagram showing how workflow view groups merge requests and where they are in the review process
A[Create a
merge request] --> B{Reviewers
added?}
B-->|Yes| D[<strong>Review
requested</strong>]
B -.->|No| C[<strong>Assigned
to you</strong>]
D -->|Approved| E[<strong>Approved
by others</strong>]
D -..->|Changes
requested| F[<strong>Returned
to you</strong>]
F -->|Author
makes changes| D
E -->G{All
approvals?}
G -->|Yes| K[Ready to merge!]
G -.->|No| J[Remains in
<strong>Waiting for approvals</strong>]
This review flow assumes:
Merge requests in one of the Active statuses count toward the total shown in the left sidebar:
These merge requests need attention from you, or a member of your team.
Reviewers have provided feedback, or requested changes.
You're a reviewer for this merge request.
You're the merge request author or assignee. You've not added reviewers yet.
The Active tab shows all your in-progress merge requests, sorted by status. These merge requests are excluded from the active count, because no action is required from you right now:
Your assigned merge requests that are waiting for approvals, and reviews you have requested changes for.
Your assigned merge requests that are waiting for approvals, and reviews you have requested changes for.
Merge requests you've reviewed and approved.
Merge requests that have received approvals from other team members.