> ## Documentation Index > Fetch the complete documentation index at: https://docs.coderabbit.ai/llms.txt > Use this file to discover all available pages before exploring further. # Views, filters, and layout > Cut a large queue down to the pull requests that are actually yours — with built-in views, search, filters, grouping, two layouts, saved views, team views, and Focus lanes. export const OpenBetaBadge = ({tip = "This feature is currently in open beta. We are actively improving it based on your feedback. If you encounter any issues or have suggestions, please share them on our Discord community or visit the support page.", title = "Open Beta", cta = "Contact support", href = "/support", disabled = false}) => { return {title} ; }; export const EssentialsPlanBadge = ({tip = "This feature is available on Essentials (formerly Pro), Team (formerly Pro+), Advanced, and Enterprise. Please refer to our pricing page for more information about our plans and features.", title = "Essentials Plan", cta = "Read more", href = "https://coderabbit.ai/pricing", disabled = false}) => { return {title} ; }; export const GitHubBadge = ({tip = "This feature is available on GitHub and GitHub Enterprise.", title = "GitHub", cta, href, disabled = false}) => { return {title} ; }; | A cross-repository queue is only useful if you can cut it down. Triage gives you four independent controls, and they compose: a **view** decides which pull requests are in play, **filters** and **search** narrow that set, **grouping and ordering** arrange what is left, and the **layout** decides how it is drawn. A [saved view](#saved-views) captures all four at once. ## Built-in views The rail down the left of the queue holds your views. Three are built in: | View | What it shows | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Requires my action** | Everything you have a part in — pull requests you authored, and pull requests where you are a requested reviewer, a reviewer, an approver, or asked for changes. This is where you land by default. | | **All PRs** | Every tracked, open pull request you can see, across every repository. | | **Safe to close** | Pull requests carrying a [close recommendation](/triage/prioritization#close-candidates) you have not already parked. | Every view is limited to pull requests that are **open** and **tracked by CodeRabbit**, in repositories you can access. There is no separate "authored by me" view. **Requires my action** is deliberately the union of your authoring and your reviewing, because in practice you want one queue rather than two. To narrow it to just your own pull requests, filter by **PR author**. Each view remembers its own grouping, ordering, and card properties, so you can keep **Safe to close** arranged by repository and oldest-first while **All PRs** stays ranked by priority. ## Search and filters **Search** — the box at the top of the queue matches pull request titles, `owner/repository` names, and pull request references like `#4312`. **Filters** — open **Filter** to narrow by any of these. Each is a multi-select: choosing several values matches any of them. | Filter | Values | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Repository name** | Any repository in the queue | | **PR author** | Any author in the queue | | **PR reviewers** | Any reviewer on a pull request in the queue | | **Priority** | `P0 · Urgent`, `P1 · High priority`, `P2 · Medium priority`, `P3 · Low priority`, `Safe to close`, `No priority` | | **Review workflow** | `New changes, unreviewed by CodeRabbit`, `Awaiting human review`, `Action required by the author`, `Ready to merge`, `Other` | | **Review guidance** | `Quick`, `Standard`, `Deep`, `Later` | | **Risk** | `High`, `Medium`, `Low` | | **Security risk** | `Critical`, `High`, `Moderate`, `Low` | | **Change type** | `Bugfix`, `Feature`, `Refactor` | | **Title** | Free text, matched as a substring against titles only — unlike search, it ignores repository names and pull request numbers. Tick **Exclude matching titles** to invert it, which is the one exclusion Triage offers. | **Clear filters** removes all of them at once. Filters live in the URL, not in your account. That means a filtered queue is a link you can paste to a colleague — and that filters are not restored when you come back later. To keep a combination, [save the view](#saved-views). ## Grouping and ordering Open **Display** to arrange the queue. **Grouping** splits it into labelled sections, and **Sub-grouping** splits those again by a second field. Both offer: | Group by | Sections you get | | ----------------- | ------------------------------------------------------------------------------------------------------------------ | | **Workflow** | `Not reviewed by CodeRabbit`, `Awaiting human review`, `Waiting on author`, `Ready to merge`, `Untracked`, `Other` | | **Priority** | `P0` through `P3`, plus `Safe to close`, `No priority`, and `Untracked` | | **Security risk** | The five risk levels, plus `No current Security review` | | **Repository** | One section per repository, busiest first | | **Author** | One section per author, busiest first | | **Focus** | `Now` and `Next` — see [Focus lanes](#focus-lanes) | | **None** | One flat list | **Ordering** sorts within each group by **Priority**, **Last activity**, **Created**, **PR number**, or **Title**, ascending or descending. Grouping and ordering are applied to the whole queue **before** it is paged, so page two continues exactly where page one stopped rather than re-sorting a slice. Sections can be collapsed, and a collapsed section stays collapsed as you move around. Hold Alt while collapsing to collapse every section at once. ## List and board **List** is one row per pull request, 100 to a page — the denser view, and the better one for reading down a ranking. **Board** is a column per group, 20 cards to a column, starting with six columns and loading more on request — the better one for seeing the shape of the queue, such as how much is waiting on authors versus waiting on reviewers. Switching layout does not change which pull requests are in the queue, only how they are drawn. ## Card properties **Display > Display properties** turns individual card fields on and off. Some fields are always shown and are not listed there. The full set, and what each one means, is in [Cards and signals](/triage/cards). ## Saved views A saved view captures a whole working setup — filters, layout, grouping, ordering, visible card properties, and which sections are collapsed — under a name and an icon of your choosing. Saved views appear in the left rail below the built-in ones. * **Save current view** stores what you are looking at now. * **Update from current** overwrites a saved view with your current setup; **Rename** and **Delete** do what they say. * Saved views are **personal**. They belong to you within one organization and are not shared with your team. * You can keep **50** of them, with names up to 100 characters. At the limit, **Save current view** is disabled until you delete one. A saved view stores the *definition*, not the result. Reopening it re-runs its filters against the current queue, so it shows you what matches today — not the pull requests that happened to be there when you saved it. ## Team views When team views are enabled for your organization, the rail carries a **Teams** section listing the GitHub teams you belong to. Selecting one scopes the queue to the pull requests where **that team is a requested reviewer** — the team's review backlog, rather than everything its members happen to be involved in. Team views work inside **All PRs** only. Your team memberships are read from your own GitHub account and refreshed periodically; if your GitHub authorization has lapsed, Triage asks you to reconnect rather than showing you a partial list. Team views are rolling out per organization, so the **Teams** section may not be there yet. ## Focus lanes Grouping by **Focus** splits the queue into two lanes: | Lane | What is in it | | -------- | ---------------------------------------------------------------------------------- | | **Now** | As much of the top of the ranked queue as fits within the author's daily capacity. | | **Next** | Everything beyond that. | "Capacity" is not a setting anyone configures. Triage measures each author's recent throughput — how much review-complexity their merged pull requests carried over the last 30 days — and fills **Now** from the top of the ranked queue until that budget is spent. Once something does not fit, everything after it goes to **Next**, including smaller work that technically would have fitted; the lane boundary is a line in the ranking, not a knapsack. Because the ranking is different for each person, the same pull request can be **Now** for its author and **Next** for one of its reviewers. That is intended: each of you has a different queue and a different budget. ## What's next Look up what every card property means before you decide which ones to show. Act on the queue you just built, without leaving it. Understand the ranking that decides the order inside every group.