#Your review queue

▍review-queue120×32

review-queueA section named Needs My Review holding twelve merge requests drawn from eight different projects, each row showing approvals, head pipeline status and a plain-language blocker.

#What you see

One query covers every project on the instance, including the ones you had forgotten you have access to. It returns in about 4.6 seconds on gitlab.com and costs 37 of the 250 complexity points GitLab allows a request.

Three columns decide whether a row is yours to act on:

• ✓ approvals. 2/2 means it has what it needs. 0/1 means it is still waiting.
• CI. The head pipeline's status, returned with the merge request rather than fetched separately.
• BLOCKER. Why it cannot merge, in words. ci failed and conflicts belong to the author, so the row can rule itself out without being opened.

#What you can do

Key	Action	Key	Action
j k	move	v	approve or unapprove
Enter	focus the preview	m	merge
o	open in the browser	c	comment
Y	copy the URL	C	check out the branch
/	filter the loaded rows	r	refresh this section

#Narrowing the queue

One filter is worth adding: press f and add draft:false. A draft merge request with you on the reviewer list is a work in progress that names you, not a review request.

The same question narrows to a group or a single project, and stays one query. Press b, Enter on platform, then f and review:requested. Press P and it is a tab.

review:unreviewed separates the merge requests you have not looked at from the ones you looked at and sent back. GitLab's own substatus wording appears on the row either way.

#The two sibling groups

Same table, different relationship to you. Both are groups on Home:

• Your merge requests, meaning what you authored or were assigned.
• Returned to you, meaning reviewers responded and it is your move again.

#The empty state

▍review-queue-empty120×32

review-queue-emptyAn empty section showing a glyph, the message 'Nothing needs your review', a restatement of the query that produced it, and two keys.