Todos
Track server tasks on a kanban board with buckets, assignees and due-date reminders.
Overview#
Todos give your team a shared task board. Cards are dragged between columns on the dashboard, grouped into buckets that can be restricted to specific roles, and handled from Discord with the /todo commands. A task with a due date sends the person responsible a reminder when it comes due.
Todos may not be available on every server yet. See Beta Features if you cannot find it in your dashboard.
How to Set Up#
- Go to the dashboard and select your server
- Navigate to the Todos section
- Optionally open the bucket manager and create buckets: one board per team or project
- Give each restricted bucket the roles that may see or manage it
- Click New Todo to add a task: title, description, assignee, due date and priority
- Drag cards between columns as work progresses
- Your team can also work the board from Discord with the
/todocommands
The Board#
Each bucket is its own kanban board with three columns:
| Column | Meaning |
|---|---|
| Open | Not started |
| In Progress | Someone is working on it |
| Completed | Done |
Drag a card between columns to change its status, or drag it within a column to reorder. Removing a card takes it off the board entirely.
Cards#
Each todo carries:
- Title and an optional description
- Assignee: the member responsible
- Due date: optional, and what triggers the reminder
- Priority: Low, Medium, High or Urgent, shown as a colored dot
- Bucket: which board it lives on
Overdue cards are highlighted so they do not quietly slide past their date.
Filtering by Assignee#
The board toolbar (the strip holding the bucket tabs) carries an Assignee row of avatars, one for everyone with a todo in the current bucket. Click one to narrow the board to their cards, click more to include them too, and use Unassigned for the cards nobody has picked up. The column counts follow the filter, so you can see at a glance how much of someone's work is still open.
The filter only hides cards; it changes nothing for anyone else and is cleared when you leave the page. Dragging a card while a filter is active still puts it where you dropped it relative to the cards you can see. The hidden ones keep their order.
Buckets#
A bucket is a separate board with its own tab, name, description and accent color. Use them to keep the mod team's work apart from the events team's, or one project apart from another.
Per-Bucket Role Permissions#
Each bucket can grant roles one of two levels:
| Level | What it allows |
|---|---|
| View | See the bucket, its todos and its reminders |
| Manage | See it, and create, edit and move todos in it |
The role list is what decides whether a bucket is public or restricted:
- Leave the role list empty and the bucket is public: everyone who can see Todos sees it
- Add a role with View and the bucket becomes restricted: only the listed roles, plus server managers, can see it, its todos and its reminders
- Manage grants add editing rights without hiding anything. A bucket whose only grants are Manage roles is still public
Restrictions apply everywhere, not just on the dashboard: a bucket you cannot see is also absent from /todo list and from the bucket picker in /todo new.
The Default Bucket#
Every server has a default bucket. It is always public and cannot be deleted, because it is where todos land when another bucket is removed. Deleting a bucket does not delete its tasks: they move to the default bucket, which does mean they become visible to everyone.
Due Dates and Reminders#
Set a due date on a todo and the bot will send a reminder when it arrives.
- The reminder goes to the assignee, or to the creator if nobody is assigned
- It arrives as a direct message
- If that DM cannot be delivered (most often because the member has DMs from server members turned off), the bot falls back to the channel the todo came from, but only for server todos in a public bucket. A personal todo, or one in a role-restricted bucket, is never posted into a channel
- Completing, removing or clearing the due date cancels the reminder; changing the date reschedules it
Due dates are set on the dashboard. Discord has no date picker inside a form, so /todo new deliberately does not ask for one. The confirmation reply links you to the board instead.
Slash Commands#
| Command | What it does |
|---|---|
/todo new | Opens a form to create a task: title, type (server or personal), bucket, and notes |
/todo list | Shows the board as a paged list, filterable by status, scope and bucket |
/todo assign | Assigns a task to a member by todo ID |
/todo complete | Marks a task completed by todo ID |
/todo remove | Removes a task by todo ID |
/todo details | Shows everything about one task: status, priority, due date, description, creator, assignee |
Every command replies privately, so running them will not clutter a channel. Todo IDs are shown on the board, in /todo list, and in the confirmation you get when a task is created.
Server vs Personal Todos#
/todo new asks whether the task is a server todo or a personal one.
- Server todos go on the server board, in a bucket, and are visible to anyone with access to that bucket
- Personal todos are yours alone: they live on your own task list rather than the server board, and only you (or someone you assign) can see them
/todo list defaults to the server board; switch its scope to see your personal tasks instead.
Who Can Change What#
- The creator of a task can always change it
- The assignee can update, complete and remove it
- Anyone with Manage on the task's bucket, and server managers, can change anything on that board
Trying to act on a task you cannot reach gives a clear refusal rather than silently doing nothing.
Tips#
- Assign every task with a due date. The reminder goes to the assignee, so an unassigned task only ever nags the person who created it.
- Tell your team to keep DMs from server members enabled, otherwise due-date reminders cannot reach them and fall back to a channel, or nowhere at all, for private buckets.
- Use buckets before you use priorities. Splitting work by team is usually clearer than one giant board where everything is Urgent.
- Keep the default bucket for general work. Anything sensitive belongs in a restricted bucket, since deleted buckets dump their tasks into the default one for everyone to read.
- Grant Manage sparingly. View is enough for people who just need to know what is happening; Manage lets them move and edit other people's tasks.
- Work the board from Discord for quick updates.
/todo completeis much faster than opening the dashboard when you finish something mid-conversation. - Note the todo ID when you create a task: every command that acts on an existing task takes the ID.