Your queue¶
Review lists every container that has a submission open or in flight, bucketed by state and sorted so the oldest waiting decision is at the top.
The buckets¶
| State | Label | What it means |
|---|---|---|
| Awaiting your decision | Awaiting your decision | A review merge request is open and findings wait on a reviewer. Sorted oldest first. |
| Blocked | Blocked, returned to engineering | A hard gate failed. Nothing to decide; it is with engineering. Shown so you know why it is not in your list. |
| Ready | Cleared, ready to record | Every finding is decided and none rejected. The authorization can be recorded. |
| Decided | Decided | Authorized or rejected. |
| In pipeline | Scan in progress | A run is under way. |
Tiles at the top count each bucket, and the age of the oldest waiting item. The sum of the tiles equals the number of containers in review.
Claims¶
Open a container and claim it. A claim tells the rest of the team that you are working on this one, so two people do not review the same package. Claims are not locks: one lapses after thirty minutes without activity, and an administrator can release a stuck one, which is recorded with a visible note.
Claiming needs your GitLab connection, because the claim is recorded against your identity. If you are not yet connected, the console offers the connect step at that moment.
Not yet submitted¶
A container that has scan results but no open merge request appears under its application, not in your queue, marked as not yet submitted. You can open it and read it as a preview, but there is no decision to record until it is submitted.
Freshness¶
The header shows when the console last read from GitLab. Data older than fifteen minutes is marked stale. An administrator can trigger a refresh; the console also refreshes on its own schedule and on pipeline events.