Table view
Route: /org/tasks?view=table · Permission: View Tasks
1. What the table view is
A spreadsheet of the same tasks — columns you choose and put in your own order, most of them editable in place. It exists for the job the other views are bad at: changing the same field on many tasks in a row without opening anything.
The view switcher tooltips it plainly: "Table View (inline edit)".
| Table (this page) | List | Kanban | |
|---|---|---|---|
| Editable fields | 13 | 4 | Status only |
| Columns | Your choice and order, horizontally scrolling | Your choice and order, collapsible | Statuses |
| Selection and bulk actions | No | Yes | No |
| Pagination footer | No | Yes | No |
| Row actions | Comments only | Four | Two |
2. How the table fits the workspace
It shares filtering and grouping with the List view — the same helpers drive both, so a filter set in one behaves identically in the other.
3. Using the table — step by step
Step 1 · Read the columns
The columns below are in their default order. Everything is shown until you choose otherwise, except Logged and Created.
| # | Column | Editable | Control |
|---|---|---|---|
| 1 | Type | ✅ | Select |
| 2 | Key | — | The task reference. Always shown |
| 3 | Risk | — | The task's risk badge |
| 4 | Summary | ✅ | Text input. Always shown |
| 5 | Status | ✅ | Select — limited to permitted transitions |
| 6 | 💬 | — | Opens comments. Tooltip "Open comments" |
| 7 | Assignee | ✅ | Select, Unassigned default |
| 8 | Priority | ✅ | Select |
| 9 | Category | ✅ | Select, — when unset |
| 10 | Due date | ✅ | Date |
| 11 | Start date | ✅ | Date |
| 12 | Est (h) | ✅ | Number, min 0, step 0.5 |
| 13 | Rem (h) | ✅ | Number, min 0, step 0.5 |
| 14 | Value | ✅ | Number — only in a project that puts a value on its tasks |
| 15 | Milestone | ✅ | Select, — when unset |
| 16 | Billable | ✅ | Toggle |
| 17 | Tags | ✅ | Tag chips with an add… input |
| 18 | Logged (h) | — | Hours logged so far. Off until you tick it |
| 19 | Created | — | The day the task was created. Off until you tick it |
Step 2 · Choose and order the columns
Click Columns beside the search box.
- Tick or untick a column to show or hide it. The table redraws at once.
- Drag the handle on the left of a row to move that column. Its place in the list is its place in the table, left to right.
- Tick all / Untick all at the foot, and Reset to default to go back to the order above.
Key and Summary carry a lock: they can be moved but never hidden, so the table always says which task a row is. Untick everything else and those two remain.
Your choice is saved for you, not for the project or the team. It follows you to another browser and survives signing out; a colleague opening the same project sees their own. The List view keeps a separate choice of its own.
Put Value beside Due date, then filter to Due date before Today — see Filtering and grouping. A saved view keeps the filter; the columns stay as you left them.
Empty: No tasks match the current filters.
Step 3 · Edit a cell
Every edit saves as soon as you commit it — there is no Save button and no undo:
| Control | Commits on |
|---|---|
| Type, Status, Assignee, Priority, Category, Milestone | Choosing an option |
| Due date, Start date | Changing the date |
| Est (h), Rem (h) | Leaving the field |
| Summary | Leaving the field, or Enter |
| Billable | Toggling |
| Tags | Enter or comma; Backspace on an empty input removes the last |
Unchanged values are not sent — retyping the same summary or estimate makes no request.
The table is the fastest way to change a lot of tasks and the fastest way to change the wrong one. The activity history records what changed, which is the only way back.
Step 4 · Change status
The status select offers only the transitions the workflow permits from the row's current status — the illegal ones are not in the list at all.
Kanban refuses an illegal drop silently. Here the illegal options simply are not offered, which makes a mis-drawn workflow obvious immediately.
Step 5 · Group
Group rows span the full width and collapse on click, showing a colour dot — or the person's avatar
when grouping by assignee — the group name, and (n).
Step 6 · Scroll
The table is wider than the window by design; it scrolls horizontally with a sticky header row.
4. Field reference
Where each select's values come from
| Column | Source |
|---|---|
| Type | Task types |
| Status | Statuses, filtered by the workflow |
| Assignee | Project members |
| Priority | Priorities |
| Category | Task categories |
| Milestone | Project milestones |
Est (h) and Rem (h)
Est is the estimate; Rem is remaining effort. Both accept half-hour steps and refuse negatives. They are re-keyed on every save, so a value corrected by the server is reflected rather than left as you typed it.
What the table does not have
| Missing | Use instead |
|---|---|
| Checkbox selection and bulk actions | List view |
| Pagination controls | List view's footer — the table shows the same page |
| Log Time | List view or Kanban |
| Add Subtask | List view |
| A description column | The detail panel |
5. The admin contract
Editing a column needs the permission for that field, exactly as elsewhere:
| Column | Permission |
|---|---|
| Status | Change Status of Task |
| Assignee | Manage Task Assignment / Allow Change Task Assigne |
| Due date | Change Task Due Date |
| Est (h) | Change Estimation of a Task |
| Everything else | Edit Tasks |
6. Downstream
An inline edit is an ordinary task update: it appears in the activity history, sends the same notifications, and a status change runs the workflow's actions and conditions.
7. Don't confuse this with…
| Thing | Where | Why it is different |
|---|---|---|
| Table view (this page) | ?view=table | Inline editing, no selection |
| List view | ?view=list | Selection, bulk actions, pagination |
| Bulk actions | Bulk actions | Same change to many tasks at once, from the list |
| Timesheet grid | My Timesheets | Hours per day, not task fields |
The table is one task at a time, quickly. Bulk actions are twenty tasks at once, in a single operation. They look like the same job and are not.
8. Troubleshooting
| Symptom | Cause |
|---|---|
| A status is missing from the dropdown | The workflow does not permit it from the current status |
| A cell will not accept input | The matching field permission is missing |
| An edit disappeared | It saved, then the server returned a corrected value |
| No checkboxes | The table has no selection — use the list |
| No page controls | The table shows the list's current page |
| Columns run off screen | It scrolls horizontally by design — or hide the ones you do not need with Columns |
| A column is missing | It is unticked in Columns. Value also needs the project to put a value on its tasks |
| A colleague sees different columns | Column choices are per person |
| Hide Done left tasks visible | The table matches by hard-coded status id — see Filtering |
Related
- List view · Bulk actions
- Workflow — why some statuses are missing