Docs / Boards & tickets
Boards & list view
Every project has one or more boards. Each board has its own columns and ticket key, and you can view it as a kanban board or as a grouped list.
Boards and columns
A project can hold several boards, for example one per team or per product. Each board has a key (like XA) that prefixes its ticket numbers, and its own columns. The last column counts as done: filters, progress bars and GitHub automation use it.
Manage boards and columns in Settings → Boards. Project owners, admins and managers can do this.
Tickets
- Drag cards between columns, or change the status from the ticket.
- A ticket can have an assignee, priority, epic, labels, due date, story points, subtasks, links to other tickets, attachments, comments and logged work.
- The Activity tab records every change, including changes made by AI agents and by GitHub.
- Large boards load page by page as you scroll, so every ticket is reachable.
Ticket types
| Type | Use it for |
|---|---|
| Task | Regular work. This is the default. |
| Bug | Something broken. |
| Feedback | Comments from users, often sent through the Feedback SDK. |
| Feature | A request for something new. |
Set the type when you create a ticket or from the ticket itself. To filter by type, use the Type filter or type:bug.
List view
Switch from Board to List in the board header to see tickets as rows in groups, similar to GitHub Projects.
- Group by epic (the default), status, assignee, priority, type, or no grouping.
- Each group can be collapsed and shows a progress bar for its done tickets.
- Change the assignee, status and priority directly in the row.
- + Add item at the bottom of a group creates a ticket that already belongs to that group.
- By default the list hides finished work with
-status:done. Clear the filter to show everything. See Filtering & search.
Moving to another board
Use Move to board on a ticket to move it to another board in the same project. The ticket gets the new board's key. Its old key still works for search and GitHub links, because ticket numbers are unique within a project.
Tickets from the Feedback SDK
Reports sent through the Feedback SDK appear on the board with a Reported via panel. The panel shows the app, the reporter, the page they were on, their browser and any console errors. Find these tickets with source:sdk.
Get told about new reports
In Settings → Notifications, each person chooses email and in-app alerts for bug reports, feedback and feature requests. Owners and admins get bug reports by email by default.