Docs · topic 8 of 12 · For whoever runs it
Recurring tasks
Standing work that puts itself on the wall before it's due.
Why
Monthly generator tests, quarterly filter changes, the Friday backup check — work that never arrives as a request but eats real hours. Recurring tasks put it on the wall automatically, so the board reflects what the team is actually carrying.
Setting one up
Admin → Recurring tasks → Add. A recurring task has a title and description, a category, an assignee (or the pool), size, priority, severity, and a schedule:
- Daily, Weekly (pick the day), or Monthly (pick the day of the month). Pick the hour it should appear.
- Lead days — how far ahead of the due date the note should show up. A monthly task due on the 1st with 5 lead days appears on the 26th, due the 1st.
Each occurrence is a normal ticket. Finish it like any other. The next one is generated on schedule whether or not the last one was closed — an unfinished occurrence is a signal, not a blocker.
Pausing
Untick Active to stop generating without deleting the definition and its history.