Team Issue Cycles
Configure Team planning windows, assign Issues, review progress and capacity, and manage rollover and calendar feeds.
Cycles are Team-owned planning windows for grouping Issues into a fixed period. They give a Team an upcoming/current schedule, a shared Issue view, progress and success graphs, lightweight capacity guidance, rollover automation, and an optional calendar feed.
Cycles belong to Integrity. They do not mirror Linear cycles, change Linear Project dates, or turn an estimate into a delivery promise.
Enable Cycles Owner Admin
Cycle settings live under Team settings -> Cycles.
Open the Team
Open Workspace Settings -> Teams, select the Team, then choose Cycles.
Configure the schedule
Enable Cycles, then choose the duration, start weekday, cooldown between cycles, and how many future cycles Integrity keeps ready.
Choose automation
Decide whether active Issues with due dates, started Issues, or completed Issues are automatically added to the current planning window.
Each Team owns its own Cycle settings. Sub-Teams do not inherit a parent Team's schedule.
Open a Cycle
When Cycles are enabled, the Team sidebar shows the current cycle and Upcoming. The Cycles overview displays the Team schedule as a timeline, including configured cooldowns and visible pauses.
A Cycle detail page contains:
- The Issues currently assigned to that Cycle.
- Shared filters, display properties, grouping, and ordering for the Team.
- Scope, started, completed, success, and capacity summaries.
- A progress graph for current and completed work.
- Cycle description and resource links.
- Actions for editable names, descriptions, dates, links, Favorites, and calendar feeds.
Local table changes remain private until you select Save. Current Team members can publish the shared Cycle view. Reset restores the saved Team view.
Assign Issues
When Cycles are enabled for an Issue's Team, Cycle appears in Issue create, detail properties, and table cells. Choose a cycle or No cycle.
An Issue belongs to at most one active Cycle at a time. Moving it preserves membership history so completed-cycle scope and Activity remain understandable after later rollover.
Automation can add eligible Issues to the current Cycle. During a real pause between Cycles, automation targets the first upcoming Cycle. Automatic changes are labeled Cycle automation in Issue Activity.
Unresolved Team Triage intake is never added by Cycle automation and does not appear in Cycle Issue lists, graphs, or capacity. It becomes eligible only after an authorized Triage acceptance or route resolves the intake overlay.
Change the schedule
Upcoming Cycle dates can be moved without allowing two active Cycles in the same Team to overlap. Integrity previews the impact before applying a schedule change.
- Moving an upcoming Cycle can shift that Cycle and every later active Cycle by the same amount.
- Extending the current Cycle moves future Cycles when overlap would otherwise occur.
- Shortening the current Cycle can keep later dates and create a visible Cycles paused gap, or move later Cycles earlier while preserving their duration and spacing.
- Start cycle today is available only for the first upcoming Cycle during a real gap.
Expired Cycles close through the Team's timezone-aware rollover process. Unfinished Issues move forward through the same membership history and Activity contract.
Progress, success, and capacity
Cycle graphs use stable daily snapshots of visible Issue scope and completed work. Weekend intervals are marked separately, and current progress carries through the Team-local current day.
Success counts completed scope fully and started scope partially. Capacity uses an explicit Cycle capacity value when one is set; otherwise Integrity uses recent completed/closed Cycle velocity as guidance.
Capacity is planning guidance, not a staffing commitment, SLA, delivery date, or forecast. Hidden or inaccessible Issues never contribute to the values shown to you.
Calendar feed
When calendar feeds are enabled, Team managers can generate, regenerate, or revoke a private Cycle feed token. The feed contains Cycle names and dates only. It does not include Issue titles, descriptions, estimates, members, or private Team content.
Treat the feed URL like a secret. Regenerate or revoke it if it is shared accidentally.
Activity, audit, and privacy
Manual assignment, movement, removal, automation, and rollover appear in Issue Activity with event-time Cycle snapshots. Cycle settings, schedule, lifecycle, and resource changes appear in the Team Audit log.
Private Team boundaries still apply. Non-members and direct-share-only Issue readers cannot enumerate a private Team's schedule, graph, capacity, resources, calendar token, or hidden Issues. Direct-shared Issue Activity uses redacted Cycle references when needed.