Back to app
Task details

Task details

Run a single task — edit metadata, manage checklists and subtasks, comment, and change status.

Reviewed OperatorVertiqa 1.54+

The task detail page is the working surface for one piece of work — the description, the people on it, the steps, the time, the links, and the conversation. It's a two-column layout: the main column holds the work, and a right-hand rail holds the task's properties.

Layout

The main column, top to bottom:

  • Header — status badge, title, and Edit, Watch, and more (Edit / Delete) controls.
  • Description — what the task is.
  • Checklist — tick-box sub-items inside this task. Best for one-task-with-many-steps situations.
  • Subtasks — full child tasks with their own status, priority, and assignment. Best when a step is itself non-trivial work.
  • Dependencies and Related tasks — link this task to others in the same project (see Dependencies and related tasks).
  • Files — attachments for this task.
  • Comments — running conversation log for context, decisions, and async handoffs.

The right rail:

  • Properties — status, assignee, reporter, priority, start date, due date.
  • Type — the work item type (Bug, Feature, Chore, …) applied to this task, or No type (see Work item types).
  • Time — log time against the task and track it versus the estimate (see Time tracking).
  • Recurrence and Tags.

Common tasks

  1. Edit metadata — title, description, priority, start/due dates.
  2. Change status — pick from the selector; the kanban will reflect it.
  3. Assign to a teammate — they'll see the task in their Mine view.
  4. Set the type — categorize the task from the Type card.
  5. Watch the task — click Watch to follow it; the button reads Watching (with the watcher count) once you do. Watchers are notified when the task changes. Click again to stop watching.
  6. Log time — use the timer or a quick entry in the Time card.
  7. Add a checklist item for each step inside the task. Tick them as you go.
  8. Promote a checklist item to a subtask when it grows into its own piece of work.
  9. Comment to leave context. Comments are visible to everyone who can see the task.

Checklist vs subtask — which?

  • Use a checklist item when the step is small and only matters in the context of this task.
  • Use a subtask when the step has its own owner, due date, or status worth tracking separately.