Recurring tickets

Create a ticket that repeats every week, every second week, on the first or last weekday of the month, every second month, every quarter, or every year; how each occurrence gets its dates, when its ticket is created, and how to change, pause, or end the series.

Written for
user
Roles
owner, admin, member, project-manager, agent
Requires
Workspace users who may start tickets on the project create a series; The series owner, a Project manager on the project, or an Owner or Admin edits, pauses, resumes, or archives it
Feature
tickets

A recurring ticket is a series: a rule that says how often, a length that says how long each occurrence runs, and the ticket fields every occurrence is created with. SAQ creates one ordinary ticket per occurrence, a little ahead of its start date. Once created, each ticket stands on its own: close it, reassign it, move it, or delete it, and the series carries on unchanged. Recurring tickets are for operational work and follow-ups (the weekly backup check, the monthly report, the quarterly review, the yearly certificate renewal) and for planning: a series with an assignee and an estimate is counted in resource planning long before its tickets exist.

Before you start

  • You need to be a workspace user (Owner, Admin, or Member) who may start tickets on the project. Client users, elevated or not, cannot create or see series. A series always belongs to a project; there are no recurring Inbox tickets.
  • The series is created as you: you are its owner, the reporter of every ticket it creates, and its tickets are created with your permissions. If you later lose the project, the series pauses; an Owner, Admin, or Project manager can hand it to someone else.
  • A workspace holds at most 200 series that are not archived.

Steps

  1. Select New (or press c), choose a Project, and enter a Title and the other fields as for any ticket. Or open Recurring in the sidebar and select New recurring ticket.
  2. Under Repeat, tick Create this ticket on a schedule.
  3. Set the First start date: the first occurrence. Every later occurrence is counted from it. It cannot be in the past.
  4. Choose how it Repeats (see the table below). Options that need a particular weekday position, such as "Every month on the first Friday", are only offered when the first start date is such a day.
  5. Set the Length of each occurrence in days, weeks, months, or years. The due date of every ticket follows from it: the form shows "First ticket: 2 Oct 2026 – 2 Oct 2026" as you type.
  6. Optionally change Create ahead (how many days before each start date the ticket is created; 14 by default, at most 90) and set an Ends date.
  7. Select Create recurring ticket. The first ticket opens; the series is listed under Recurring.

Fields

Field Meaning Rules and default
First start date The start date of the first occurrence; the anchor of the whole series Required. Today or later. Every later occurrence is derived from it, never from the previous ticket, so a skipped or deleted ticket cannot drift the schedule.
Repeats The rule Every week, second, third, or fourth week on the anchor's weekday; every month on the first, second, third, fourth, or last such weekday, or on the anchor's day of the month; every second month, every quarter, every half year, on the anchor's day of the month; every year on the anchor's month and day.
Length How long each occurrence runs A whole number of days, weeks, months, or years. Due date = start date + length − 1 day, so a one-day task is due on its start date and a one-week task started on Monday is due on Sunday. The length may not exceed the interval between occurrences.
Create ahead Days before each start date the ticket is created 0–90, default 14. The first ticket is created at once, whatever this says. A yearly task with 90 days ahead appears three months before it is due to start.
Ends Last possible start date Optional. No occurrence starts after it; the series then shows as Ended.
Title, Description Copied onto every ticket As for any ticket.
Kind, Priority Copied onto every ticket Default: the first kind in the workflow and the workspace default priority.
Assignee Copied onto every ticket A workspace user, or a client user elevated on the project. If they can no longer be assigned when a ticket is created, that ticket is created unassigned and the series says so.
Estimate Copied onto every ticket Workspace users only, and only while time tracking is on. Leaf tickets only, as always. This is what resource planning reads.
Parent ticket Every occurrence becomes a sub-ticket of it Optional. Set from the parent's page with New sub-ticket, or through the API (parentId). Cannot itself be a recurring occurrence. If it is archived or deleted later, new tickets are created without a parent and the series says so.
Labels Copied onto every ticket Through the API (labelIds) at creation; labels removed from the workspace later are simply left off.

Day-of-month rules clamp to the month's length: a series anchored on 31 January runs on 28 (or 29) February, 31 March, 30 April. A yearly series anchored on 29 February runs on 28 February in ordinary years.

What the rule offers

Choice in the form (with a Friday as first start date) Rule Longest length allowed
Every week on Friday weekly, interval 1 1 week (7 days)
Every second week on Friday weekly, interval 2 2 weeks (14 days)
Every third / fourth week on Friday weekly, interval 3 / 4 3 / 4 weeks
Every month on the first Friday monthly, interval 1, weekday position 1 1 month, 4 weeks, or 28 days
Every month on the last Friday monthly, interval 1, weekday position last 1 month, 4 weeks, or 28 days
Every month on day 2 monthly, interval 1 1 month, 4 weeks, or 28 days
Every second month on day 2 monthly, interval 2 2 months, 8 weeks, or 56 days
Every quarter on day 2 monthly, interval 3 3 months, 12 weeks, or 84 days
Every half year on day 2 monthly, interval 6 6 months, 24 weeks, or 168 days
Every year on 2 October yearly 1 year, 12 months, 52 weeks, or 365 days

The second, third, and fourth weekday positions exist too (through the API, ordinal 2–4); the form offers first and last. The 4th Friday of a month is sometimes also its last: the form and the API check that the first start date really holds the position you chose.

The series page

Recurring in the sidebar lists every series in the workspace with its rule, next occurrence, owner, and status; a filter shows Active, Paused, Ended, or Archived series (archived ones are hidden otherwise). Each series has a page with:

  • the rule in words ("Every second week on Friday"), the length, the first start date, the next occurrence, the lead time, and the end date;
  • the Upcoming occurrences: the next six start and due dates the rule will produce;
  • the Tickets created from it, newest first, in the same table as any ticket list;
  • for people who may edit it: Edit series, Pause / Resume, and Archive series.

A ticket that belongs to a series carries a repeat mark on boards and in lists and a Repeats row on its page that states the rule, such as "Every second week on Friday", and links to the series.

Rules

  • Each ticket is independent. Closing, reopening, editing, moving, archiving, or deleting a ticket changes nothing on the series, and the series never changes a ticket it has created. A ticket you delete is not created again.
  • When tickets are created. The first ticket is created when you save the series. Every later one is created within the hour once the day that is lead time days before its start date arrives, in the workspace's time zone. If several occurrences fall into that window at once (a short weekly series with 14 days of lead), they are all created, oldest first. Each new ticket notifies its assignee like any other new ticket.
  • Dates come from the rule. An occurrence's start and due dates are set by the series. Moving a parent on the project timeline leaves its recurring sub-tickets where they are and lists them as unchanged. You can still edit an occurrence's dates by hand on its page; that does not affect the series.
  • No sub-tickets under an occurrence. A recurring ticket cannot become a parent ("A recurring ticket cannot have sub-tickets"), and its own parent is set on the series, not on the ticket ("A recurring ticket takes its parent from its series"). Everything else works as on any ticket: links, comments, attachments, time, viewers.
  • Editing the series changes only the occurrences not created yet; existing tickets keep their title, assignee, and dates. Changing the rule or the first start date restarts the schedule: the next occurrence becomes the first date on or after today that the new rule produces. A date that already has a ticket is skipped, never duplicated.
  • Pausing stops creation until you Resume. Resuming never backfills: the next occurrence is moved to the first one on or after today, and the occurrences missed while paused are not created.
  • Ending and archiving. A series past its Ends date shows as Ended and creates nothing more. Archive series closes it for good: its tickets stay, it leaves the default list, and it cannot be resumed or edited.
  • When the owner cannot create the ticket. If the owner has left the project or the workspace, or the kind or priority has been archived, the series pauses at that occurrence and its page says why ("Paused: the owner may no longer start tickets on this project. Hand the series to someone else and resume it."). An Owner, Admin, or Project manager changes the Owner under Edit series, then resumes.
  • Who may edit a series. Its owner, a Project manager on its project, and Owners and Admins. Others see it read-only.
  • Planning. Occurrences with an assignee and an estimate are counted in resource planning: the tickets that exist as allocated time, and the ones the rule will still create as projected time, so a yearly or quarterly task is visible in the plan all year.
  • Export and deletion. Series are part of the workspace export and are purged with the workspace.

Examples

Every Friday, one day. A support team creates "Weekly backup check" on Friday 2 October with Every week on Friday, length 1 day, and the default 14 days ahead. The tickets for 2 and 9 October exist at once; the one for 16 October appears on 2 October. Each is due on its own Friday and is closed when done.

Quarterly review, two weeks long. "Quarterly security review" is anchored on 1 October with Every quarter on day 1, length 2 weeks, and 30 days ahead. The ticket for 1 January is created on 2 December, due 14 January. With an assignee and an estimate of 16 hours, resource planning shows those 16 hours spread over the two weeks of every quarter of the coming year.

Last Friday of the month under an epic. From the page of ACME-300 Operations 2026, New sub-ticket opens the form with the parent preselected; the person ticks the schedule, picks Friday 30 October as the first start date, and chooses Every month on the last Friday. Every month-end ticket becomes a sub-ticket of ACME-300, whose estimate roll-up grows with them.

Through the API: POST /api/w/acme/recurrences; through MCP: create_ticket with repeat. See the API reference and the MCP page.

Common problems

  • "A recurring ticket needs a start date: the first occurrence." Set the first start date before saving.
  • "The first start date cannot be in the past." Pick today or a later date; the first ticket is created at once.
  • "The length may not exceed the interval between occurrences." A weekly task cannot run eight days; shorten the length or choose a wider rule.
  • "The start date does not fall on the chosen weekday position of its month." "First Friday" needs a Friday in the first seven days of the month; the form disables positions the date does not hold.
  • "The series ends before it starts." The end date is before the first start date.
  • "A recurring ticket cannot have sub-tickets." You tried to place a ticket under an occurrence. Use the series parent instead, or a plain ticket.
  • "A recurring ticket takes its parent from its series." The parent of an occurrence is edited on the series.
  • "A workspace has at most 200 recurring series; archive one first." Archive series you no longer need.
  • "The series is archived." Archived series cannot be edited, paused, or resumed. Create a new one.
  • The series shows "Needs attention". Open it: a paused series says what happened and what to do. "The latest ticket was created without an assignee" or "… without the parent ticket" means the series kept going but with that field left off; fix the assignee or the parent under Edit series.