Recurring series

A recurring series is a rule, a length, and a ticket template; SAQ creates one independent ticket per occurrence ahead of its start date.

Written for
user, admin, integration-developer
Roles
owner, admin, member, project-manager, agent
Requires
Feature
tickets

A recurring series is the object behind a recurring ticket: a rule anchored on the start date of the first occurrence, a length that gives every occurrence its due date, a lead time that says how many days before its start date each ticket is created, and the template fields (title, description, kind, priority, assignee, estimate, labels, parent) every ticket is created with. An occurrence is one date the rule produces; its ticket is an ordinary ticket that remembers which series and which occurrence it came from.

How it relates to other concepts

  • A series belongs to one project and to one owner, a workspace user. Its tickets are created as the owner, who is their reporter and therefore a viewer, with the owner's permissions at that moment.
  • Every ticket the series creates carries the series id and the occurrence date, shows a repeat mark, and links back to the series. Otherwise it is a ticket like any other: it has a kind, a state, a priority, comments, time, links, and billing fields.
  • The series may name a parent ticket; every occurrence becomes its sub-ticket through the ordinary parent link. An occurrence never has sub-tickets of its own.
  • An occurrence's estimate and assignee make it count in resource planning; occurrences the rule will still produce are counted there as projected time.

Rules

  • Rules. Weekly with an interval of 1–4 on the anchor's weekday; monthly with an interval of 1, 2, 3, or 6 on the anchor's day of the month (clamped to shorter months) or on the anchor's weekday at position 1–4 or last; yearly on the anchor's month and day (29 February becomes 28 February). Every occurrence is derived from the anchor and the rule, never from the previous ticket.
  • Length. A whole number of days, weeks, months, or years. Due date = start + length − 1 day. The length may not exceed the interval: weekly rules allow up to the interval in weeks (7 × interval days); monthly rules up to the interval in months, 4 × interval weeks, or 28 × interval days; yearly rules up to one year, 12 months, 52 weeks, or 365 days. Two occurrences of one series therefore never overlap.
  • Lead time. 0–90 days, default 14. The first ticket is created when the series is created; each later ticket within the hour once start − lead time has arrived in the workspace's time zone. A series has a cursor, the next occurrence without a ticket, that only ever moves forward: nothing is backfilled, a deleted ticket is not re-created, and resuming a paused series moves the cursor to the first occurrence on or after today.
  • Independence. The series never edits, closes, or re-creates a ticket it created. Editing the series affects only occurrences not created yet; a rule or anchor change restarts the cursor from today, skipping dates that already have a ticket.
  • States. Active; paused (by a person, or by the system when the owner can no longer create the ticket, with the reason on record); ended (past its end date); archived (closed for good, read-only, tickets kept).
  • Access. Workspace users see every series in the workspace. The owner, a Project manager on the project, and Owners and Admins edit, pause, resume, and archive it. Client users never see series. API tokens with write may create and edit; pause, resume, and archive are browser-only.
  • Limits. At most 200 series per workspace that are not archived; at most 12 tickets per series per hourly run, so a long backlog catches up over several hours.

Example

"Monthly invoice run" is anchored on Friday 30 October 2026 with the rule every month on the last Friday, a length of 3 days, a lead time of 7 days, and an estimate of 4 hours for Kari. On 23 October the ticket for 30 October (due 1 November) exists. On 20 November the ticket for 27 November appears. Resource planning shows Kari's 4 hours on the last Friday of every month of next year as projected time until each ticket is created, and as allocated time after.