Insights and views
Saved views
Filter a project's builds list, save the filters as a view, and keep views and pinned projects in your sidebar.
A project's builds page can be narrowed with filters. A saved view keeps a set of filters under a name, so "Rejected builds on release branches" is one click in the sidebar instead of four chips every time. Views are yours alone: nobody else in the workspace sees them.
Filter the builds list
Section titled “Filter the builds list”Open a project from the sidebar to see its builds, newest first. The find field in the page header filters by free text: a build number, a pull request, a commit, a build name, a branch or an author.
Below the header, a row of chips filters by:
| Chip | Choices |
|---|---|
| Status | Needs review, Approved, Rejected, Processing, Failed, Expired. Needs review filters by the review, not the build's state, so a failed build with no decision can appear under it |
| Branch | Pick from the branches builds were made on, or type part of a name |
| Author | Text |
| Reviewer | Text |
| Build name | Text |
| Date | From and To dates (whole UTC days) |
Each chip fills in once it's set and has a small clear button. Clear filters removes them all. The filters are kept in the address, so you can send a filtered list to someone.
Display options (ShiftV) change how the list looks without changing which builds it holds:
- Group by: No grouping, Status, Branch, Author or Day.
- Order: Newest first, Oldest first, Most changes, or Needs attention first.
- Show: Branch and commit, Author, Time and Change counts.
These are remembered in your browser. j and k move through the list, x selects a build, Space peeks at it, f focuses the filters, and Enter opens it. With several builds selected, a bar offers Approve, Reject and Request review; see Reviewing a build.
Save a view
Section titled “Save a view”-
Set at least one filter. The Save view button appears next to Clear filters.
-
Click it. The dialog lists the filters it will save and asks for a Name (up to 80 characters).
-
Click Save view. A toast says "Saved view" with the name.
The view belongs to the project whose list you filtered and appears in the sidebar under Your views. A view saved from the workspace-wide builds list has no project: it covers every project and shows each build's project. When the current filters already match a saved view, the button gives way to "Saved as" and its name.
Open and use a view
Section titled “Open and use a view”Choose it under Your views in the sidebar, or search for it with CommandK (saved views are listed under Go to). It opens that builds list with the view's filters applied, under a Views breadcrumb. You can change the filters on that page to look around, but those changes last only for the visit: a view isn't edited by browsing it. To keep a variation, set the filters on the project's own list and save again under a new name.
If a view is deleted, or belongs to someone else, its address shows "This view doesn't exist".
Pin a project in the sidebar
Section titled “Pin a project in the sidebar”This is separate from views. The sidebar keeps Pinned projects above the rest. Right-click a project in the sidebar and choose Pin project or Unpin project. Pinned projects are per person and per workspace, like views. The same menu has Builds, Triage, Baselines, Sites (when the project has some), Project settings (owners and admins) and Leave project.
Where this lives
Section titled “Where this lives”Views and pinned projects are specific to one workspace: switch workspace in the sidebar and you see that workspace's own. They belong to your account, so they follow you across browsers and devices, unlike the display options above, which are stored in the browser. See Account settings for the other things that are yours.