Skip to content

Parallel Cycles #422

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
danciaclara wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Parallel Cycles #422

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions docs/core-concepts/cycles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,6 +81,33 @@ Any unfinished work items in the ended Cycle will remain in their current state.

This manual control gives you the flexibility to adapt your Cycles to your team's actual work rhythm, rather than being strictly bound to predetermined dates.

## Run parallel cycles <Badge type="warning" text="Enterprise Grid" />

By default, only one cycle can be active at a time, and cycles cannot have overlapping dates. With parallel cycles enabled, you can run multiple cycles simultaneously with overlapping date ranges. This is useful when your team manages parallel workstreams — for example, a two-week sprint running alongside a longer release cycle.
Copy link
Copy Markdown

@coderabbitai coderabbitai bot Mar 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Clarify this as an exception to earlier “no overlap / one active cycle” rules across the page.

This section is accurate, but the page still contains absolute statements earlier (e.g., Lines 19, 42, 61, and 145) that conflict with Enterprise Grid behavior. Please update those earlier lines to say “by default” or explicitly scope them to when parallel cycles are disabled, so the document is internally consistent.

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docs/core-concepts/cycles.md` at line 86, Update the earlier absolute
statements that claim "only one cycle can be active at a time" and "cycles
cannot have overlapping dates" so they are scoped as exceptions — e.g., prepend
"By default," or add "when parallel cycles are disabled" — ensuring every place
where those rules are stated (the earlier absolute claims on the page) is
changed to the conditional phrasing to match the new sentence about "With
parallel cycles enabled"; keep wording consistent with the new line about
parallel cycles running simultaneously.


### Turn on parallel cycles

1. Go to **Project Settings > Features > Cycles**.
2. Toggle on **Parallel cycles**.

![Parallel cycles setting](https://media.docs.plane.so/cycles/parallel-cycles-setting.webp#hero)

Once enabled, you can create cycles with overlapping dates and start multiple cycles at the same time. Each active cycle appears independently in the Cycles page with its own progress breakdown and burn-down chart.

![Multiple active cycles](https://media.docs.plane.so/cycles/multiple-active-cycles.webp#hero)

### How parallel cycles work

Even with parallel cycles enabled, a work item can only belong to one cycle at a time. This prevents duplicate tracking and keeps cycle metrics accurate. If you try to add a work item that already belongs to another cycle, the system will block the action.

When you end a parallel cycle, you're prompted to choose what happens to incomplete work items — leave them in the ended cycle or transfer them to an upcoming cycle.

Parallel cycles also appear in the workspace-level Active Cycles view and in any connected Teamspace Cycles view, so managers can track overlapping cycles across projects.

### Turn off parallel cycles

If you turn off the parallel cycles toggle after overlapping cycles already exist, those cycles continue to run normally. You just won't be able to create new overlapping cycles going forward. No existing data is disrupted.

## Transfer work items

Once the due date of an active Cycle passes, it’s automatically marked as completed. After that, you can easily transfer any unfinished work items to an active or upcoming cycle, making it simple to move any leftover tasks to the next cycle.
Expand Down
Loading