List view
Route: /org/tasks?view=list (the default) · Permission: View Tasks
1. What the list view is
A dense, hierarchical row list — the only view that shows parent and child tasks nested, and the only one with real pagination.
Each row carries six inline controls that edit the task in place, so most day-to-day changes never need the detail panel.
| List (this page) | Kanban | Table | |
|---|---|---|---|
| Hierarchy | Nested and expandable | Flattened with a breadcrumb | Nested |
| Pagination | Server, 50 per page | Per-column Load More | Inherits the page |
| Inline edit | Six controls | Log time, comment | The widest set |
| Selection | Yes — checkboxes | No | No |
| Default? | Yes |
2. How the list fits the workspace
3. Reading the list — step by step
Step 1 · The header row
| Column | Holds |
|---|---|
| Title | Expand chevron, title, category chip and billable pill |
| Effort Rem. | Remaining hours. Tooltip: Remaining: <n>h |
| Progress | Percentage. Tooltip: Progress: n% (Est: xh | Act: yh) |
| Status | Inline control |
| Priority | Inline control |
| Tags | Inline control |
| Assignee | Inline control |
| Action | Log Time · Add Comment · Add Subtask · Edit Task |
Columns, beside the search box, chooses which of these appear and in what order — tick, untick and drag, exactly as in the Table view. The list can also show Due date, Start date, Milestone, Estimate, Logged, Created and — in a project that puts a value on its tasks — an editable Value. The list keeps its own choice, separate from the table's, and it is saved for you alone. Title and Action are always shown.
Each header is a button — "(Click to Expand)" in its tooltip. On a narrow window they collapse automatically, and clicking one pins it open. Useful when you care about progress and nothing else.
Step 2 · Expand the hierarchy
A task with subtasks shows a chevron. Expanding indents the children under it, and they carry the same inline controls.
As soon as Group by is anything other than No Grouping, nesting is disabled and every task —
parent and subtask alike — becomes a flat row inside its group.
That is why a task can appear to "move out from under" its parent when you group.
Step 3 · Edit inline
Four of the columns are editable controls, each tooltipped with its current value —
Status: In Progress, Priority: High, Tags: a, b, Assignee: ….
Each is gated by its own permission:
| Control | Permission |
|---|---|
| Status | Change Status of Task |
| Priority | Edit Tasks |
| Assignee | Manage Task Assignment / Allow Change Task Assigne |
| Tags | Edit Tasks |
Step 4 · Row actions
| Action | Opens |
|---|---|
| Log Time | The log-time modal |
| Add Comment | The comment modal |
| Add Subtask | The create drawer with this task as parent |
| Edit Task | The detail panel |
Step 5 · Select and act
Checkboxes select rows. A selection enables the bulk actions bar, and lets you drag the selection onto a category in the left rail.
Step 6 · Page through
The footer reads Showing 1 - 50 of 214 tasks with previous and next buttons. Pages are 50 tasks.
A heading reading (12 tasks) means twelve on this page. With 214 tasks across five pages, no
heading ever shows the project-wide total.
4. Field reference
Group headings
Present whenever Group by is set. Each heading shows a coloured ring, the group name, and
(n tasks). Headings are collapsible, and grouping by category adds an ADD TASK button on
hover that opens the create drawer pre-filled with that category.
What Progress is calculated from
actual_hours ÷ estimated_hours, expressed as a percentage and capped at 100.
A task at 100% has consumed its estimate. It says nothing about whether the work is finished — a task can be at 40% and done, or at 100% and barely started.
For completion, use the status. For effort overrun, this is the column.
A task with no estimate divides by one, so any logged time reads as a very large percentage — one more reason estimated hours is required at creation.
The Title cell
| Element | Shown when |
|---|---|
| Expand chevron | The task has subtasks and grouping is off |
| Checkbox | Always |
| Title | Always |
| Category chip | The task has a category |
BILLABLE pill | The task is billable |
5. The admin contract
| Prerequisite | Without it |
|---|---|
| View Tasks | No page |
| Change Status of Task | The status control is read-only |
Manage Task Assignment / .changeassigne | The assignee control is read-only |
| Create Tasks | No Add Subtask |
| Statuses, priorities, categories | The inline controls have nothing to offer |
6. Downstream
Inline edits are ordinary task updates — they fire the same notifications, appear in the same activity history, and a status change runs the same workflow actions as a Kanban drop.
7. Don't confuse this with…
| Thing | Where | Why it is different |
|---|---|---|
| List view (this page) | ?view=list | Nested rows, six inline controls |
| Table view | ?view=table | A spreadsheet grid built for bulk editing |
| My Tasks list | /org/my-tasks | Same shape, only your work, no pagination footer |
| Progress | This column | Effort consumed, not completion |
| Effort Rem. | This column | Remaining hours, including subtasks |
8. Troubleshooting
| Symptom | Cause |
|---|---|
| Subtasks are no longer nested | Grouping is on |
| A column disappeared | It collapsed on a narrow window — click the header icon |
| Progress reads far above 100% | The task has no estimate |
| Group counts look too small | They count the current page only |
| An inline control will not open | The matching field permission is missing |
| A selection was lost | Changing page clears it |
| Nothing happens on Add Subtask | Missing Create Tasks |
Related
- Bulk actions — what a selection unlocks
- Filtering and grouping
- Task detail