Skip to content

Commit da6951c

Browse files
committed
minor edits
1 parent ba3c6e6 commit da6951c

File tree

1 file changed

+2
-75
lines changed

1 file changed

+2
-75
lines changed

docs/core-concepts/cycles.mdx

Lines changed: 2 additions & 75 deletions
Original file line numberDiff line numberDiff line change
@@ -62,79 +62,6 @@ Once a cycle is active and contains issues, you can monitor its progress, assess
6262

6363
![Track cycle progress](https://media.docs.plane.so/cycles/track-cycle-progress.webp#center)
6464

65-
<div className="tag-wrapper">
66-
## Cycle Progress Charts
67-
<Tags
68-
tags={[
69-
{ name: "Pro", additionalClass: "pro" }
70-
]}
71-
/>
72-
</div>
73-
74-
This feature provides powerful visualization tools to help you track project cycles more effectively. With real-time insights, you can see exactly how your cycle is performing against the planned progress, making it easier to stay on top of deadlines and adjust as needed.
75-
76-
![Cycle progress charts](https://media.docs.plane.so/cycles/cycle-progress-charts.webp#center)
77-
78-
### Cycle summary
79-
80-
At the top left of the cycle page, you’ll see the overall progress percentage. Hover over it to get a breakdown of completed and pending issues, along with the number of days left in the cycle. Click anywhere on the header to view all the issues within that cycle.
81-
82-
On the left, there’s a color-coded summary that shows if the cycle is leading or trailing based on the burn-down and build-up metrics. This gives you instant feedback on how things are going and highlights risks so you can make quick decisions and ensure nothing slips through the cracks.
83-
84-
Hover over the state group names on the left to see the chart update and reflect progress for that group. Clicking on a group will filter the cycle by that specific state. Additionally, when you hover over the **Scope** label, you’ll instantly see the percentage of scope change for the day it occurred.
85-
86-
As you hover over any point on the chart, you'll see daily progress metrics, while the persistent blue line shows how the scope has changed over time.
87-
88-
The **More details** pane still provides you with a full overview, including the cycle’s description, progress, and team participation.
89-
90-
The burn-down and build-up charts are straightforward ways to gauge your cycle’s momentum. You can customize them to show progress based on the **count of issues** or **point estimates** for each task, giving you the flexibility to use the metrics that work best for your team.
91-
92-
- **Scope**
93-
This is the total number of issues planned for the current cycle.
94-
95-
- **Unstarted**
96-
The issues that haven't begun yet.
97-
98-
- **Backlog**
99-
All issues in the Backlog state.
100-
101-
The other metrics are detailed below, tailored to each chart type.
102-
103-
### Burn-down chart
104-
The burn-down chart gives you a clear visual of how much work remains in your cycle. It's designed to show the ideal pace of progress compared to what’s actually happening.
105-
106-
- **Today's ideal pending**
107-
This shows how many tasks should be left based on the ideal progress for today.
108-
109-
- **Pending**
110-
This is the total number of unfinished tasks, calculated by subtracting completed tasks from the total planned for the cycle. The chart tracks the days left, so you can see what should be done by now versus what actually is done.
111-
112-
- **Leading**
113-
If your team is ahead of schedule, meaning you have fewer pending tasks than expected, the chart will show a green upward trend. The area between the ideal and pending lines is filled with light green, indicating strong progress.
114-
115-
- **Trailing**
116-
If progress is behind schedule and there are more pending tasks than expected, the chart displays a red downward trend. A light red fill appears between the ideal progress and the pending lines, signaling the need to catch up.
117-
118-
119-
### Build-up chart
120-
The build-up chart helps track how much work has already been completed in the cycle.
121-
122-
- **Today's ideal done**
123-
This shows how many issues should be completed by today based on the ideal pace.
124-
125-
- **Done**
126-
This is the total number of tasks your team has completed so far.
127-
128-
- **Leading**
129-
If you’ve completed more tasks than planned, the chart will show a green upward trend. The area between the ideal and completed lines is filled with light green, visually highlighting that you’re ahead of schedule.
130-
131-
- **Trailing**
132-
If fewer tasks are completed than expected, the chart shows a red downward trend, with a light red fill between the ideal and actual lines, indicating the need to speed up progress.
133-
134-
:::caution[Limitation]
135-
In shorter cycles, it can be harder to spot trailing trends early. To avoid falling behind, it’s important to rely on real-time updates and team communication.
136-
:::
137-
13865
<div className="tag-wrapper">
13966
## Active cycles across projects
14067
<Tags
@@ -145,11 +72,11 @@ In shorter cycles, it can be harder to spot trailing trends early. To avoid fall
14572
</div>
14673

14774
If you have multiple projects with Cycles running at the same time, you can easily track the progress of all active cycles in the **Cycles** section under the **Workspace** section in the sidebar. This gives you a quick overview of each project’s progress and helps you spot any potential issues early on. Each cycle displays its status—whether it’s ahead of schedule or falling behind—based on the burn-down and build-up metrics.
148-
![Active cycles](https://media.docs.plane.so/cycles/active-cycles-ui.webp#center)
75+
![Active cycles](https://media.docs.plane.so/cycles/active-cycles-across-projects.webp#center)
14976

15077
## Archive cycles
15178
You can archive completed cycles, allowing you to conceal significantly older cycles from your views.
15279

15380

15481
## Delete cycles
155-
You can delete a Cycle to remove it entirely. When you do, all associated analytics and progress reports will be erased. Any issues linked to that Cycle will also be automatically unlinked.
82+
You can delete a Cycle to remove it entirely. When you do, all associated analytics and progress reports will be erased. Any issues linked to that Cycle will also be automatically unlinked.

0 commit comments

Comments
 (0)