Recurring Tickets
Set up scheduled tickets that automatically create on a cron schedule — for weekly reviews, recurring tasks, and operational chores.
Recurring tickets are templates that automatically generate new tickets on a schedule. Use them for predictable, repeating work that would otherwise need manual creation each time.
Use cases
- Weekly support inbox review
- Monthly billing reconciliation check
- Daily backup verification
- Quarterly knowledge base audit
- Bi-weekly team retrospective preparation
- End-of-day escalation triage
Creating a recurring ticket
Go to Tickets → Recurring.
Click New Recurring Ticket.
Fill in the template fields — title, description, type, priority, assignee, and labels. These values are copied to each generated ticket.
Set the schedule using a cron expression or the visual schedule picker.
Optionally set a start date and end date to bound when tickets are generated.
Click Save & Activate.
Schedule configuration
Visual picker
The visual picker covers the most common patterns:
| Pattern | Description |
|---|---|
| Daily | Every day at a set time |
| Weekdays | Monday–Friday at a set time |
| Weekly | A specific day of the week at a set time |
| Bi-weekly | Every two weeks on a specific day |
| Monthly | A specific day of the month (1st, 15th, last day, etc.) |
| Quarterly | First day of each quarter |
Cron expression
For custom schedules, enter a cron expression directly. FutureBase uses standard 5-field cron format:
┌─────── minute (0–59)
│ ┌───── hour (0–23)
│ │ ┌─── day of month (1–31)
│ │ │ ┌─ month (1–12)
│ │ │ │ ┌ day of week (0–6, 0=Sunday)
│ │ │ │ │
* * * * *Examples:
| Cron | Meaning |
|---|---|
0 9 * * 1 | Every Monday at 9:00 AM |
0 8 * * 1-5 | Every weekday at 8:00 AM |
0 10 1 * * | First of every month at 10:00 AM |
0 9 1 1,4,7,10 * | First day of each quarter at 9:00 AM |
*/30 * * * * | Every 30 minutes |
All schedules run in UTC. Use the timezone offset field to adjust for your local time.
Template fields
Each generated ticket inherits these values from the template:
| Field | Notes |
|---|---|
| Title | Can include dynamic tokens (see below) |
| Description | Markdown supported |
| Type | task, feature, bug, improvement |
| Priority | Copied as-is to each generated ticket |
| Assignee | Team member or AI agent |
| Labels | All template labels are applied |
| Status | Always starts as backlog |
Dynamic tokens in titles
Use tokens in the title to include the generation date automatically:
| Token | Output |
|---|---|
{{date}} | ISO date (e.g., 2025-10-01) |
{{week}} | Week number (e.g., W40) |
{{month}} | Month name (e.g., October) |
{{year}} | Year (e.g., 2025) |
Example title: Weekly inbox review — {{date}}
Generated ticket title: Weekly inbox review — 2025-10-06
Managing recurring tickets
Viewing scheduled tickets
Go to Tickets → Recurring to see all your schedules. Each row shows:
- Template title
- Schedule (human-readable description)
- Next run time
- Last generated ticket (with link)
- Active / paused status
Pausing a schedule
Toggle the Active switch on any recurring ticket to pause it. No new tickets will be generated until you re-enable it. Tickets already created are unaffected.
Editing a template
Edits to the template affect future tickets only. Already-generated tickets are not updated retroactively.
Viewing generated tickets
All tickets generated from a recurring template are linked back to it. Open the template and click View generated tickets to see the full history.
Assigning to AI agents
Recurring tickets pair well with AI agents — create a schedule that fires a ticket every week, assign it to an AI agent, and the agent handles the work automatically with no human involvement.
Example: Weekly knowledge base audit
Template:
- Title:
Weekly knowledge base audit — {{date}} - Type:
task - Priority:
medium - Assignee:
Knowledge Base Audit Agent - Description: "Review recently added content for accuracy, completeness, and formatting. Flag any pages with outdated information or broken links."
The agent picks up the ticket, runs its review process, posts findings as an internal comment, and marks the ticket done — or escalates if it finds a significant issue.