Recurring Issues
Create ordinary Team Issues on a durable daily, weekly, monthly, or yearly schedule.
Recurring Issues create ordinary Team Issues on a durable schedule. Use them for routine evidence reviews, inspections, compliance checks, and other work that needs a new traceable Issue for every occurrence.
Each schedule owns an immutable history of its definitions and due-date occurrences. Every generated Issue keeps its own key, properties, Description, Activity, notifications, and lifecycle. Editing or stopping the schedule never rewrites an Issue that already exists.
Integrity creates the first Issue when you create the schedule. Later Issues are eligible after their scheduled due date passes in the Team's timezone.
Understand the schedule Admin Editor Viewer
A recurring schedule has:
- A root Issue definition and up to 25 direct sub-Issue definitions.
- A repeat interval from 1 through 12 days, weeks, months, or years.
- An original calendar anchor that keeps month-end and leap-year schedules stable.
- One immutable version for each meaningful edit.
- One occurrence record for each scheduled due date.
- One stable settings link that does not change when you rename the schedule.
Monthly and yearly schedules stay anchored to the original calendar day. For example, a schedule anchored on January 31 uses the last valid day in shorter months and returns to the 31st when that date exists.
Read generated Issue history Admin Editor Viewer
Generated Issues behave like manually created Issues. Their Activity identifies the scheduled due date and explains that future occurrences create separate Issues. Eligible Inbox and email notifications reuse the ordinary Issue notification rules.
A directly shared private Issue can show display-safe creation context without exposing the private Team's schedule directory, definition, count, route, or management actions.
Edit future work only Admin Editor
Editing a schedule creates a new immutable version for future occurrences. Existing generated Issues and their Activity remain unchanged.
Changing the next due date starts a new anchor for future calculations. Stopping a schedule removes it from active recurring work and prevents new occurrences while preserving its versions, occurrence history, Logs, and generated Issues.
Related
Create and edit recurring Issues
Create, duplicate, edit, bulk-align, or stop schedules.
Manage and troubleshoot
Use the Team directory, understand permissions, and recover failed occurrences.
Create Issues
Review the ordinary Issue creation fields reused by recurring schedules.
Dates and deadlines
Understand manual Issue due dates and deadline notifications.
Issue Activity
Read generated-Issue creation evidence and later work history.