List View (Table)
The default view shows issues in a paginated table with sortable columns:
| Column | Description |
|---|---|
| Priority | Color-coded indicator (Low, Medium, High) |
| Title | Issue name, clickable to open |
| Assignee | Avatar with name tooltip |
| Release | Version this issue targets |
| Cycle | Current cycle assignment |
| Status | The status of the issue’s type: writing status for a specification or a plan, development status for a task or a bug. Specifications and plans also show their realization |
| Labels | All applied labels |
| Platform | Backend, Frontend, etc. |
| Estimated | Time estimate in days |
| Spent | Time logged in days |
Click any column header to sort. Click again to reverse. Sort state persists in session.
The list is best for:
- Scanning a large backlog with filters applied
- Comparing estimates across issues
- Bulk-selecting issues for batch updates
Kanban View (Board)
The board groups tasks and bugs by development status in columns. Specifications and plans, which have no development status, appear in a separate Writing zone, grouped by writing status, and nothing disappears from the cycle because of it. Each card shows:
- Title
- Priority indicator
- Labels
- Assignee avatar
Drag cards between columns to update the status directly on the board: the development status in the columns, the writing status in the Writing zone.
The board is best for:
- Daily standups (“what is in progress?”)
- Visualizing flow across the status pipeline
- Quick status updates without opening issues
My Issues
My issues in the sidebar lists the open issues assigned to you. A Role selector changes what “mine” means:
| Role | Shows |
|---|---|
| Assigned to me (default) | Issues assigned to you |
| Assigned to my team | Issues assigned to your team |
| Created by me | Issues you created |
| To test by me | Issues where you are the tester |
A second selector switches between Open (default) and All (finished issues included). The same page exists for any teammate through the “Filter by” selector, which now picks the assignee, like in a cycle.
Active Filters
Every filter a list is under shows as a chip below the toolbar: the rules of the table filter, the person, the role and the state, and the implicit scope of the home page (“Current cycle and unfinished issues of previous cycles”). Click the × of a chip to remove it, or Clear all to remove every filter at once.
Counter and Cards
The count under a list or a board is the number of cards you see. On a cycle board, issues without a status, or whose status has no column on the board, are no longer hidden: they appear in a read-only Status not on the board column, which does not accept drops. On the developer dashboard, a column that shows only its first five cards says so (“5 of 8”), next to a See all link to your issues.
Cycle User Filter
The person a cycle is filtered on is remembered from one visit to the next, for every cycle, and shown as a chip. Choose All in the selector, remove the chip or use Clear all to forget it. If that person has left the organization, the filter is dropped with a notice.
Column Labels
In dense tables the column titles collapse to icons. Each icon keeps a tooltip over the whole label and a text readable by screen readers, and the selection and actions columns have labels too. The Cycle column shows the cycle name.
Switching Views
A toggle in the top-right of the issue list switches between List and Kanban. Your active filters, sort, and search apply to both views. Switching views does not reset your filters.
Bulk Operations (List View)
In list view, check the box on any issue to select it. Select multiple issues to enable bulk actions:
| Action | Description |
|---|---|
| Set status | Update the status for all selected. A status applies to a type: development status for tasks and bugs, writing status for specifications and plans |
| Assign | Reassign all selected to a user or team |
| Set release | Move selected issues to a different release. Issues that are in a capability are skipped and counted, because they follow the release of their capability |
| Set cycle | Reassign selected to a different cycle |
| Add label | Add a label to all selected issues |
| Set platform | Update platform for all selected |
Bulk operations are irreversible in a single action, so confirm before applying to large selections.
Display details
- The priority shown on an issue page is the same as in the list and the kanban. An issue without priority says “No priority”.
- The status shown on an issue is the one the capability page shows.
- Comments have an always-visible “…” menu (edit, delete) and an “edited” mention once the text changed. Only the author and administrators can edit or delete a comment.