Tasks
The task board collects what your team still has to do: a ban appeal to check, a restart plan to agree on, a base report to look into. Every task has someone responsible, a due date if you want one, and a conversation where colleagues can be mentioned.
Navigation
Admin → Tasks
The board
The board has four fixed columns: Open, In progress, Waiting (blocked, or waiting on somebody else) and Done. Drag a card into another column, or within a column to change the order. On a phone the columns become tabs.
A card shows the title, the priority (urgent and high as a coloured edge and badge), the level, the server, the due date, how many comments and links it has and who it is assigned to. Your answer on a card means somebody mentioned you there and is waiting.
Lanes split the board into rows by assignee, level, server or priority. The filters narrow it down: Mine, Waiting for me, assignee, priority, level, server, overdue.
Done tasks stay on the board for two weeks after they were finished, then move to the Archive tab.
A number on a card — and on the Board and Archive tabs — counts what waits for you there: unread notifications, and mentions you have not answered yet. A mention keeps counting after you opened the task, and on a task that was finished and archived meanwhile, until you answer or mark it done.
A task
Click a card to open it. A task has:
| Field | What it means |
|---|---|
| Title, description | What is to be done. The description supports Markdown and mentions. |
| Where | The server it belongs to — or Whole organization for tasks that concern every server. |
| Level | Who may see it (see below). Without a level, everybody who sees the board sees it. |
| Priority | Low, normal, high, urgent. |
| Due | Optional. The assignees are reminded the day before at 09:00 server time and once when it is overdue. |
| Assignees | One or more people. Only people who may see the task can be assigned. |
| Links | What the task is about: a ticket, a player, a faction, a review. A linked task also shows on that ticket's and that player's page. |
Below that is the history: who created, moved, assigned or changed the task, and the comments. Entries the AI Companion or an AI app wrote in your name are marked via Companion or via MCP; changes made from Discord are marked via Discord.
Creators and assignees follow a task automatically; anyone else can follow it from the ⋯ menu. Followers hear about new comments and column changes.
Private tasks
A task can be just for you: switch it on when you create the task, or note it from Discord (below). Nobody else sees a private task, not even people who may see every task of the organization, until you share it. Private tasks sit in their own lane Just for me at the top of the board; the rest of the board is the team's.
To share one, drag it into the team lane, or open it and choose Share with the team. It then belongs to the server set under Where (or the whole organization) and needs the right to create tasks there. A team task cannot be made private again.
Everybody who may see the board can keep private tasks, even without the right to create team tasks.
From Discord
On a Discord server connected to dzbot you can turn a message into a task without leaving Discord:
- Context menu: right-click a message (on a phone: press and hold) →
Apps→ Save as task. A form opens with the title and description taken from the message, and Where: just for you, the whole organization, or one of your servers — only the places where you may create team tasks are offered. - 👀 reaction: react with 👀 to note the message at once as a private task. dzbot sends you a direct message with Add details, which opens the same form.
The task always links back to the message. Noting the same message again edits the task you already have instead of creating a second one; removing the 👀 does not delete it. Both only work for people who may see the task board of that server; your Discord account has to be linked to your dzbot account.
Mentions
Type @ in a comment or the description and pick a colleague. They get a notification and the task shows Your answer for them until they write on it or mark it Done, no answer needed. Only people who may see the task are offered; if you mention someone who cannot, they are not told and you see a notice.
Mentions also work in internal notes on tickets and in comments on reviews. See Notifications.
Who sees what
| Right | What it allows |
|---|---|
admin.tasks.view (per server) | See the tasks of that server, comment, mention, follow, move tasks assigned to you |
admin.tasks.manage (per server) | Create, change, assign and delete the tasks of that server |
org.tasks.view | See every task of the organization, including organization-wide ones, on every level |
org.tasks.manage | Create and change every task, including organization-wide ones |
org.tasks.levels | Manage the task levels |
The moderator template includes both server rights. Groups without a wildcard need them granted before they see the board.
Levels
Levels decide who sees a task. They work like ticket levels: whoever may see a level also sees every level below it. You define the levels once for the organization (⋯ → Task levels on the board); each level becomes a right per server, Task level · name, that you grant in the access groups. People with org.tasks.view always see every level.
With the AI Companion and AI apps
The Companion can find, create, change, move, assign, link and comment on tasks, mention colleagues and tell you what is waiting for you ("What do I still have to do?"). AI apps connected through MCP get the same tools in the tasks toolset — see Connect AI apps.