Tasks and ownership

Capture work

Member creates a Task with a clear title, initial column, priority, optional planned start and due date. Owner is one active internal member; TaskAssignees add collaborators without replacing accountability. Imports first validate column, lane, owner and date mappings in an ImportJobs preview. Board Owner accepts the mapping before execution; each source row creates at most one task under the same input identity.

Prepare the task

Member adds TaskChecklistItems, marks mandatory steps and links any same-board TaskDependencies. Distinguish the blocking task from the blocked task. Reject self-dependency and cycles before accepting the edge. Shared work needs an explicit TaskParticipants grant and active guest board membership; a mention or pasted file URL cannot add that permission.

Follow up on dates

The reminder service evaluates DueDate in the board timezone and schedules a unique NotificationDeliveries occurrence for the intended current owner or reviewer. Recheck the task, audience and date immediately before sending. Completed, cancelled, archived or rescheduled work suppresses an obsolete reminder. Provider acceptance and observed delivery remain separate, and an unknown result keeps its original operation key for reconciliation.

Reopen or archive

Board Owner can reopen completed work through an allowed current workflow move with a recorded reason. Preserve the original completion event, increment CycleNumber and start a new work cycle without rewriting earlier timings. Recheck WIP and applicable approval policy for the destination. Archiving removes a task from active lists but preserves its relationships and event history; it cannot be used to remove evidence from an open review.

Import an existing team checklist

An imported list may use display names for owners and informal column labels. Review those mappings before creating cards. Two people with the same name must resolve to distinct authenticated members; an unknown person stays an import error instead of becoming an accidental invitation.

The input hash, mapping revision and original row identity make accepted rows repeatable. Correct rejected rows through a reviewed change without recreating existing tasks. Imported tasks follow the same destination limits and access policy as manually entered cards.

Owner identifies the accountable person. Additional assignees help without replacing accountability or expanding the audience. The due date is the intended deadline in the board timezone. The schedule endpoint follows that date, so a calendar view cannot carry a second conflicting deadline. A planned start after the deadline is rejected; an undated task remains visible without an invented schedule.