Recurring Tasks
Set tasks to repeat on a schedule — daily, weekly, biweekly, or monthly. Completed tasks automatically create a new instance with the next due date.
Recurring tasks automatically create a new instance when the current one is completed. This is ideal for repeating work like weekly reports, daily standups, monthly compliance checks, or sprint reviews.
How it works
Set recurrence on a task
At creation or any time after — via @mention, slash command, or the create modal.
Complete the task
Via any method — @mention, Complete button, slash command, or auto-close from a nudge reply.
A new task is automatically created
The completion message includes the next due date:
@alice marked *Weekly standup review* as done! (next due 2026-02-27)
Setting recurrence
At creation via @mention
@Tickr create a weekly standup review task for @alice due Monday@Tickr add a daily task to check monitoring dashboards@Tickr create a monthly compliance report, assign to @bobTickr recognizes these patterns:
| Phrase | Recurrence |
|---|---|
| "every day", "daily" | Daily |
| "every week", "weekly", "every Monday" | Weekly |
| "every two weeks", "biweekly" | Biweekly |
| "every month", "monthly" | Monthly |
At creation via modal
Use the Repeat dropdown in the /tickr create modal. Options: Daily, Weekly, Biweekly, Monthly, or no recurrence.
After creation via slash command
/tickr repeat 01KH9DN3 weeklySet or remove recurrence on a task.
/tickr repeat 01KH9DN3 dailyVia @mention
@Tickr make the standup task repeat weekly@Tickr set the report task to monthly recurrenceRemoving recurrence
/tickr repeat 01KH9DN3 off@Tickr stop the standup task from recurringFrequencies and next due date
| Frequency | Next due date |
|---|---|
daily | Current due date + 1 day |
weekly | Current due date + 7 days |
biweekly | Current due date + 14 days |
monthly | Current due date + 1 calendar month (day clamped if needed, e.g. Jan 31 becomes Feb 28) |
If no due date is set, the next instance is computed from today. If the computed next date falls in the past (e.g., task was completed late), it advances from today instead to keep the cadence moving forward.
What gets cloned
| Cloned (inherited) | Not cloned (fresh each cycle) |
|---|---|
| Title | Updates / progress notes |
| Description | Dependencies / blockers |
| Assignee | Thread link |
| Priority | AI summary |
| Estimate | Snooze state |
| Tags | |
| Recurrence schedule | |
| Milestones (reset to incomplete) | |
| Subtasks (reset to incomplete) |
Completion paths
Recurrence triggers from all completion methods:
- AI @mention —
@Tickr close the weekly review - Complete button — click Complete on the task card
- Slash command —
/tickr update 01KH doneor/tickr complete 01KH - Auto-close — reply "done" to a nudge
In every case, the completion message includes the next due date.
Where recurrence appears
| Surface | How it's shown |
|---|---|
| Task cards | :repeat: Repeats weekly on the status line |
Task list (/tickr list) | :repeat: icon next to the title |
| Board canvas table | Repeat column showing the frequency |
| Board canvas details | Repeats: weekly |
| AI board context | repeats: weekly in per-task context |
Availability
Recurring tasks are available on all plans (Trial, Pro, Max).