Skip to content

Pull requests page: GitLab MRs where I'm a reviewer are missing from "Review requested" #30445

Open

Description

@fooku18

Describe the bug
For GitLab, the pull requests page's "Review requested" section shows only some of the open merge requests where I'm a reviewer. GitLab's own MR search with Reviewer = <me> returns 5 open MRs. T3 Code shows only 3 of them.

It looks like T3 Code only lists MRs where a review is still pending/requested. It leaves out MRs where I'm assigned as a reviewer but the review state differs (e.g. already reviewed).

Image Image

Steps to reproduce

  1. Connect a GitLab account that is a reviewer on several open MRs.
  2. In GitLab, filter merge requests by Reviewer = <me> → 5 open.
  3. Open the T3 Code pull requests page → "Review requested" shows 3.

Expected behavior
Every open MR where I'm a reviewer shows up on the page, matching GitLab's Reviewer = me filter.

If this is intended
If "Review requested" is deliberately limited to pending reviews, please add a separate section for MRs where I'm a reviewer, so those MRs are still visible.

Screenshots (redacted; MRs labelled A–E to match between them)

  1. GitLab Reviewer = me filter: 5 open MRs (A–E)
  2. T3 Code "Review requested": 3 MRs (D, E, B). A and C are missing.

Activity

  1. juliusmarminge commented on Nov 3, 2026

    @juliusmarminge
    Member

    I couldn't reproduce this on current main (7c22e24) with a real gitlab.com project.

    What I ran:

    • A private GitLab project with three open MRs by another user, with me as reviewer on each. The review states were unreviewed, reviewed (comment published as a review), and approved. GitLab's API reported them as UNREVIEWED, REVIEWED and APPROVED.
    • GitLab's reviewer_username=<me> filter returned all three. That is the filter T3 Code uses.
    • Pull requests page, All view, filtered to GitLab: all three were under Review requested (3), including the approved one.
    • Pull requests page, Reviewing filter: all three were listed.

    T3 Code doesn't look at the reviewer's review state. Any open MR that lists you as a reviewer should land in Review requested. One limit applies, though: the page only lists merge requests from repositories added as projects in T3 Code. GitLab's own Reviewer = me search covers every project you can access.

    To narrow it down:

    1. Are the repositories of MR A and MR C added as projects in T3 Code, and on the same GitLab host as B, D and E?
    2. If they are, do A and C show up anywhere on the page (Authored or Others), or not at all? Do they show under the Reviewing filter?
    3. Which T3 Code version are you on, and on which client (desktop, web, or mobile)?
  2. fooku18 commented on Nov 4, 2026

    @fooku18
    Author

    T3 Code doesn't look at the reviewer's review state. Any open MR that lists you as a reviewer should land in Review requested. One limit applies, though: the page only lists merge requests from repositories added as projects in T3 Code. GitLab's own Reviewer = me search covers every project you can access.

    Indeed. I have added the missing project in t3code for the missing MRs and they appear afterwards. I have to say that as a user I find it unintuitive though. In our GitLab project we have more than 700 projects and sometimes for quick fixes I start in "No Project" and let an agent fix it + open a MR even though I am not a constant maintainer. I find the PR page really useful as it allows me to not have to leave t3code but adding all projects feels cumbersome. Is there a technical restriction for this or can you potentially introduce an option?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions