Managing Tasks

Update status, complete, reassign, and list tasks using slash commands or natural language @mentions.

Once tasks exist, Tickr gives you multiple ways to manage them — slash commands, interactive buttons on task cards, and natural language @mentions.

Update a task

/tickr update <task_id> <status> [note]

Update a task's status, optionally with a progress note.

Arguments:

<task_id> — The first 8 characters of the task ID (shown on every task card and list). Prefix matching is supported — you can use fewer characters as long as it uniquely identifies the task.
<status> — One of: open, in_progress, blocked, done
[note] — Optional. A text update describing progress.

Examples:

/tickr update 01KH9DN3 in_progress

/tickr update 01KH9DN3 in_progress Finished the auth module, starting on tests

/tickr update 01KH done

ℹ️ Update quality

When you provide a note, Tickr may evaluate its quality (on eligible plans). Vague updates like "working on it" get playful pushback asking for specifics. See Update Quality.

Via @mention:

@Tickr update the login task — finished the auth module, starting tests

@Tickr mark the database migration as in_progress

Tickr matches tasks by title keywords or ID prefix. If you say "the login task" and there's only one task with "login" in the title, Tickr finds it.

Complete a task

/tickr complete <task_id>

Shortcut to mark a task as done. Equivalent to /tickr update <task_id> done.

/tickr complete 01KH9DN3

Via @mention:

@Tickr close the checkout fix

@Tickr mark the redesign task as done, final version approved by @dave

Reassign a task

/tickr reassign <task_id> @user

Transfer a task to another team member.

/tickr reassign 01KH9DN3 @carol

The mentioned user becomes the new assignee and receives future nudges for the task.

Via @mention:

@Tickr reassign the login task to @bob

@Tickr give the API migration to @carol

List your tasks

/tickr mine

Show all your active tasks across every channel. Response is private (only you see it).

Output format per task:

🔵 *Fix login timeout* — `01KH9DN3` | `in_progress`
🔴 *API migration* — `01KH8F2A` | `blocked`
⚪ *Write docs* — `01KH7G1B` | `open`

Returns "You have no active tasks. Nice!" if your plate is clear.

Via @mention:

@Tickr what am I working on?

List channel tasks

/tickr list

Show all active (non-done) tasks in the current channel. Response is public.

Tasks are sorted by priority (critical first) then by status (in-progress and blocked before open).

Via @mention:

@Tickr what's the status of everything?

@Tickr show me all blocked tasks

Tickr returns an AI-synthesized summary grouped by person, highlighting who's working on what, any blockers, and overdue tasks. Completed tasks older than 72 hours are automatically hidden.

View the board

/tickr board

Show a kanban-style board overview for the current channel.

⚪ OPEN (3)
  • *Write API docs* — @alice (`01KH9DN3`)
  • *Design mockups* — @bob (`01KH8F2A`)
  • *Setup CI* — unassigned (`01KH7G1B`)

🔵 IN_PROGRESS (2)
  • *Fix login timeout* — @carol (`01KH6E0C`)
  • *Database migration* — @dave (`01KH5D9D`)

🔴 BLOCKED (1)
  • *API integration* — @eve (`01KH4C8E`)

✅ DONE (5)
  • *Auth module* — @alice (`01KH3B7F`)
  ...

Tagging tasks

Add or remove tags to categorize tasks by work type, area, or any custom label.

/tickr tag 01KH9DN3 bug frontend

Add one or more tags to a task.

/tickr untag 01KH9DN3 frontend

Remove tags from a task.

Via @mention:

@Tickr add tags bug and frontend to the login task

@Tickr remove the urgent tag from the login task

Tag-based filtering

Filter boards by tag using natural language:

@Tickr show me all bug tasks

@Tickr what frontend work is open?

Tag filters can be combined with status filters (e.g., "open frontend tasks"). See Tags & Labels for full details.

Logging time (Max plan)

/tickr log 01KH9DN3 1.5 Code review

Log time spent on a task.

Via @mention:

@Tickr I spent 2 hours on the API task fixing endpoints

@Tickr log 1.5h on the checkout fix — code review

Tickr extracts the task, hours, description, and date from natural language. See Time Tracking for full details.

Task lifecycle

Every task flows through four statuses:

Status	Emoji	Nudge behavior
`open`	⚪	Nudged on schedule
`in_progress`	🔵	Nudged on schedule
`blocked`	🔴	Blocker is nudged instead of assignee
`done`	✅	No nudges

Transition between any status freely. See Blockers for the blocked workflow and Auto-Close for automatic completion.