Filters and saved views
A view is a saved filter, sort, grouping and layout over issues. It is a named object: it has a URL, it appears in Views, and other members of the workspace can open it.
Filtering
Section titled “Filtering”Select Filter and add conditions. Available dimensions:
| Dimension | Values |
|---|---|
| Repository | Any connected repository |
| State | Every state, Open, Closed |
| Label | Any label in scope |
| Assignee | Any GitHub account with an issue in scope, or Unassigned |
| Milestone | Any milestone, or No milestone |
| Project | Any project the connection can read |
| Project field | Single select, number, date, iteration and text fields — see below |
| Portal | Whether the issue is a request in at least one portal. Available on a saved view; the built-in Requests from portals is one |
| Text | Matches title and body; see Search |
Each active condition is a chip above the list. Remove one by selecting the cross on the chip. Conditions combine with AND; a condition with several values matches any of them.
Filtering on a project field
Section titled “Filtering on a project field”Field lists every field on every project the connection can read, under the project it belongs to. What it offers depends on the field’s type:
| Field type | You choose |
|---|---|
| Single select | One of its options, in the project’s own order |
| Number | An operator — Is, At least, More than, At most, Less than, Between — and one number, or two for Between |
| Date | An operator — On, On or after, After, On or before, Before, Between — and one date, or two for Between |
| Iteration | The iteration’s title, as it appears on the card |
| Text | The text the field holds |
Every type also offers Not set, which matches issues that have no value for
the field. A number is compared as a number, so 3 matches a stored 3.0, and
a date comparison also matches an iteration by its start date.
An iteration is typed rather than picked from a list: Pealboard is not told a field’s iterations, only the value on each card.
Sorting and grouping
Section titled “Sorting and grouping”Sort orders by updated, created, number, title or comment count — or by any project field, listed under Project field in the same control. A number sorts numerically, a date and an iteration chronologically, a single select in the project’s own option order, and a text field alphabetically. An issue with no value for the field sorts last, whichever direction you ask for.
Group by decides the columns in the Board layout; the List and Table layouts do not read it.
Saving a view
Section titled “Saving a view”- Filter, sort and group until the screen is what you want.
- Select Save as view.
- Give it a name and choose whether other members can see it.
The view’s name becomes the page title. Changing a saved view and selecting Save view updates it for everyone who can see it; Save as view makes a second one instead.
Managing views
Section titled “Managing views”Views lists every view you can see, in three groups: the six built-in views a workspace is created with, the views shared with the workspace, and your own. From it you can rename, duplicate, share and stop sharing, delete, and copy a view’s link. Edit opens the same filter and layout controls on their own page.
Sharing a view needs the admin role or above. Stopping sharing gives the view to you. Deleting a view deletes nothing else — a view is a saved question, not a container.
What a view is not
Section titled “What a view is not”A view is not a GitHub object. It exists only in Pealboard, it is one of the few things Pealboard stores that GitHub cannot, and it disappears if you delete the workspace. Nothing about your issues depends on it.