Core concepts

The vocabulary of TTM — tasks, subtasks, groups, states, owners, tags and reminders.

A few terms come up throughout the app. Learn them once and everything else clicks into place.

Tasks, subtasks and groups

You never pick these types from a menu — TTM infers them from how you write the list. A line starting with - is a task; adding spaces after the dash turns it into a subtask of the line above; a task that owns subtasks automatically becomes a group.

Groups behave as a unit where it matters: checking a group checks its subtasks in cascade, and checking every subtask marks the group as done.

Task state

Every task is either open or completed, shown by its checkbox:

• Open — still to do.
• Completed — done.

You flip the state from the check / uncheck selector above the button rows. Completing or reopening a task is what can trigger notifications and webhooks.

A task with an owner can be flipped only by its owner — or the members of the owner role — and by whoever has Manage messages on the channel. A task without an owner can be flipped by anyone who can use the list.

Owner vs. tag

These look similar but do different jobs:

• Owner — the person (or role) responsible for the task. One owner per task — and it can be several people: TTM creates a role for them (see The roles TTM creates).
• Tag — one or more users/roles mentioned on the task, e.g. people to notify when it is completed.

Reminders

A reminder attaches a schedule to a task: a date, a time and a time zone. When it comes due, TTM reminds the task’s owner — a direct message to a person, a mention in the list’s channel to a role — so nobody has to keep checking. One ping is the default, and on the Free plan it is the only kind. Repeating reminders, which add an interval and a number of repetitions, are a Premium feature that a server switches on in Configuration. Full details in Reminders.

Notifications & history

When a task is checked or unchecked, TTM can post a notification and — if you enable it — record every action in a dedicated history thread. How much noise you want is entirely up to you: see Configuration.

Permissions

By default the app’s commands follow Discord’s own visibility rules (Server Settings → Integrations). Buttons and lists, however, stay usable by anyone unless you sync permissions — after which the list becomes read-only for users who are not allowed. This too lives in Configuration.

A few actions have a rule of their own: a task with an owner is checked by its owner (see Task state above), and sealing or deleting a list from its More panel needs Manage messages on the channel (from /config lists, the /config permissions apply).