List, table and board
Issues shows every issue in every repository you connected, in one of three layouts. The scope is the whole workspace by default: cross-repository is the starting point, not something you configure per project.
Switch layout with List, Board and Table at the top of the screen. The layout is part of a view, so saving a view saves the layout with it.
A table of one row per issue: state, issue number, title, repository, labels,
the project Status, the milestone, the comment count, assignees and when it
was last updated. Numbers align, issue numbers and repository names are in a
monospaced face because you may need to copy them exactly, and labels are shown
in the colors GitHub gave them. Below 1024 px the columns that are furthest from
the title fold away and the repository and labels move under it; nothing scrolls
sideways.
The state is an icon and a word — Open, Completed, Not planned — because the difference is never carried by color alone.
Columns of cards. A board is a view: the columns come from a view’s grouping, so choosing Board without a view open offers to save one rather than showing an empty screen. Choose what the columns are with Group by, which saves the view as it changes it:
| Group by | Columns are |
|---|---|
A project’s single-select field, Status by default |
The field’s options, in the project’s own order, plus No Status |
A label prefix, such as area: |
One column per label starting with it, plus No area label |
| Assignee | One column per assignee, plus Unassigned |
| Milestone | One column per milestone, plus No milestone |
| State | Open, Completed, Not planned |
Every board has a final column for issues with no value, because the work nobody has triaged is the work a board exists to surface.
Group by on the Issues screen itself offers a project’s fields, Assignee, Milestone and State. Grouping by a label prefix is set from the view’s own editor: select Edit on the view in Views.
Dragging a card between columns sets the grouped value. If you grouped by a
project’s Status, dragging sets that field on that project item in GitHub. The
card moves immediately and the column counts move with it; if GitHub refuses the
write, the card moves back and the refusal is shown as GitHub’s own words.
A card that cannot be moved shows why rather than refusing silently: an issue
that is not an item in the project you grouped by has no Status to set, and a
milestone belongs to one repository so an issue in another cannot be given it.
Each column holds twenty cards and carries its own count and its own Show more, so paging one column leaves the rest of the board alone.
The list, with project fields as extra columns. Add a column for any field on
any project the issues belong to: Status, Priority, Iteration, and any
custom field of type Text, Number, Date or Single select. Edit a value in place.
Table is the layout to use for bulk edit.
What Issues does not show
Section titled “What Issues does not show”- Pull requests as work items.
- Issues in repositories outside the installation, including to an owner.
- Anything from a repository that is connected but not enabled on the Free plan’s three-repository limit.