Recurring tickets

Create a recurring blueprint

Open Project → Templates and add a recurring template. Give it the ticket's title, objective, context, constraints, criteria and required outcome. Choose Backlog or Ready, then a daily, weekly or monthly schedule and local time. This blueprint is separate from a manual ticket template.

The time zone starts with the app's configured zone, Europe/London by default, and is saved with the schedule. Review the next run before enabling it. New or changed schedules start strictly in the future.

What happens when due

A due template creates an ordinary ticket. It does not start a worker. Ready still has to pass readiness checks. If an earlier generated ticket remains open, the occurrence is recorded as skipped instead of creating another ticket. The template shows its next run, latest ticket and occurrence history.

Missed schedules collapse to at most the latest due occurrence, so an outage does not generate a backlog of duplicate tickets. Repeated or overlapping triggers do not create the same occurrence twice.

Time changes and pauses

Monthly dates clamp to shorter months. If a clock change removes a local time, the schedule uses the first valid minute afterward; if it repeats a time, only the earlier instant runs. Pause or archive a template to stop future creation. Restore is available; there is no hard delete. Paused and archived periods are skipped, including after a project is unarchived.

See writing tickets for the fields every generated ticket needs. Future plan packaging is not yet released.