Skip to content
JiraVision

Task fields & statuses

Every field a task carries, the allowed statuses and priorities, and bulk edits.

Task fields & statuses

Fields

  • title — required, shown everywhere the task appears.
  • description — long text.
  • status — one of todo, in_progress, review, blocked, done. Defaults to todo.
  • priority — one of urgent, high, medium, low. Defaults to medium.
  • storyPoints — integer used by velocity and burndown.
  • assigneeId — the member who owns it.
  • sprintId — the sprint it belongs to; null means backlog.
  • dueDate — optional date, surfaced on /dashboard/calendar.
  • tags — JSON array of strings, filterable.
  • createdAt / updatedAt — server timestamps, returned as UTC ISO strings.

The status and priority lists are exported from components/dashboard-kit.tsx as STATUSES and PRIORITIES, so the filters, the board columns and the API validation all agree.

Status semantics

  • todo: not started.
  • in_progress: actively being worked.
  • review: waiting on someone else (code review, design review, approval).
  • blocked: cannot proceed; the reason belongs in the description or a comment.
  • done: finished. Everything except done counts as open in the dashboard aggregates.

Creating and editing

  1. POST /api/tasks with a JSON body creates a task and notifies the assignee.
  2. PATCH /api/tasks/<id> applies a partial update. A status change to done is what the velocity and burndown calculations look for, so it moves the charts on the next render.
  3. DELETE /api/tasks/<id> removes it.
  4. POST /api/tasks/bulk applies one change to many task ids — useful after a sprint review.

Filtering

GET /api/tasks accepts page, pageSize, status, priority, assigneeId, sprintId and search. The response is { success, data, pagination }, which is what the grid and list views on /dashboard/tasks consume.

The board keeps no records of its own

The columns on /dashboard/kanban are the task statuses and the cards are rows from GET /api/tasks, newest edited first. A drag sends the new status to PUT /api/tasks/<id> — or to PATCH /api/task-instances/<id> when the card is one day's occurrence of a schedule.

Tags

Tags are free-form strings stored as JSON. Use them for cross-cutting concerns (tech-debt, a11y, onboarding) rather than duplicating a status.