Every business has work that repeats. Sending invoices on the first of the month. Submitting quarterly tax returns. The Monday morning status meeting. The end-of-year bookkeeping close. If you've ever written "send invoices" on a sticky note — or worse, forgotten and remembered on the 5th — recurring tickets are for you.
A recurring ticket is a template that automatically spawns a real ticket on a schedule you define. You set it up once. The system creates the task for you, assigns it, gives it a due date, and drops it onto your project board. When you're done, you mark it complete — and next period, a fresh one appears.
Why not just use a calendar reminder?
Calendar reminders tell you about a task. Recurring tickets are the task. There's a difference.
A reminder pops up, you dismiss it, and now the work lives in your head. A ticket lives in your project, tracks its status, carries comments and attachments, and stays visible to your team. When a client asks "did you submit our VAT return this quarter?", you don't scroll through calendar history — you open the project and look at the ticket.
Reminders also don't survive team handoffs. If the person with the reminder leaves or goes on vacation, the reminder goes with them. A recurring ticket lives in the project. Anyone with access sees it. Anyone assigned can complete it.
Daily, weekly, monthly, quarterly, yearly
The five cadences cover virtually everything that repeats in a business:
- Daily — standup notes, end-of-day time log review, checking overnight deploys.
- Weekly — Monday planning, Friday status reports, weekly backups verification.
- Monthly — invoices, expense categorisation, financial close, client retainer reports.
- Quarterly — tax filings, performance reviews, strategic planning, audit prep.
- Yearly — annual returns, insurance renewals, domain renewals, contract reviews.
Each cadence advances from the last run date. If your anchor is the 1st of the month, every generated ticket gets the 1st as its due date. If you need the 15th instead, pick the 15th. The system follows whatever anchor date you give it and handles edge cases like months with fewer days automatically.
Lead time: see it before it's due
Some work needs runway. "Submit quarterly taxes" isn't something you want to discover on the due date itself — you want it on your board a week earlier so you actually have time to prepare.
Every recurring ticket has a lead time setting. Set it to 7 days on a monthly "Send invoices" ticket, and the task will appear on the 25th with a due date of the 1st. You get a week's warning, the due date on the ticket is still accurate, and nothing sneaks up on you.
For daily tasks, lead time stays at zero — you don't need to see tomorrow's standup ticket today. But for anything longer than weekly, even a small lead time changes the feel of the work from reactive to prepared.
Open tickets don't block the next one
Here's a design choice worth explaining: if you haven't finished last month's recurring ticket, this month's still appears anyway.
We thought about this. The alternative would be to skip periods when the previous one is still open — "you didn't finish March, so we won't create April." But that hides the problem. If you're behind on monthly invoices, the worst thing we can do is stop showing you the backlog. You should see "March invoices" and "April invoices" sitting next to each other on your board, so it's obvious you need to catch up.
Each period spawns its own independent ticket. Complete them in any order. The schedule never pauses just because you're behind.
Set up, assign, forget
Creating a recurring ticket is three fields of setup: name, frequency, and the milestone it belongs to. Everything else — assignee, initial status, description, lead time — is optional.
You get to the recurring tickets page from any project's actions menu. From there, create a new one, fill in the form, and it's live. The worker runs daily and generates anything that's due. Pause it when you're on holiday, resume when you're back. Delete it when a client contract ends.
The work that never stops coming back
Most agencies lose time not on hard problems but on routine ones. The same invoice sent fifty times. The same quarterly filing prepared eight times. The same weekly report written every Friday. Each one takes fifteen minutes to set up, and those fifteen minutes compound across months and years.
Recurring tickets take the setup out of the equation. You describe the work once. The system handles the rest — forever, or until you tell it to stop.