Task tracking

Added
Purpose
Record a piece of work to be done so it can be found, picked up and finished.
Operational principle
If a member writes down a piece of work, it exists as an item that others can see, take and move through its states; it stays until someone finishes it.
State
  • title: Task -> one Title
  • specification: Task -> opt Text
  • project: Task -> one Project
  • assignee: Task -> opt User
  • label: Task -> set Label
  • priority: Task -> opt Priority
  • dueDate: Task -> opt Date
  • createdBy: Task -> one User
Actions
  • createTask A member records a piece of work in a project, with its title and, in the same act, its assignee, labels, priority and due date.
Misfits
  • A task that nobody picks up stays open indefinitely, and a backlog of them is read as noise rather than as work.
  • A task cannot be labelled, prioritised or assigned without first being created, nor assigned without a project; everything is decided at once or not at all.
  • What counts as finished is in the title, not in the record, so two people can disagree about whether a task is done.
  • A task that turns out impossible or unwanted has no way to end; the sequence it moves through has one terminal state, so it is marked done untruthfully or left open.
  • A due date sits passively on the task, so a deadline approaches and passes unnoticed unless someone checks the list while there is still time to act.
Also called
to-do, issue, ticket, work item
Depends on
Running a project