Skip to main content

​
Overview

Cycles (also called Sprints) help teams maintain momentum by organizing work into time-boxed iterations. Track progress with burndown charts, monitor team velocity, and manage workload distribution across cycles.
Cycles provide a structured way to plan and execute work in regular intervals, typically ranging from 1-4 weeks.

​
Creating a Cycle

Set up a new cycle with essential details:
1

Open Cycles View

Navigate to your project and click on “Cycles” in the sidebar.
2

Create New Cycle

Click “New Cycle” and fill in the cycle details.
3

Configure Properties

Set the cycle name, description, start date, end date, and assign team members.

​
Cycle Properties

Name & Description

Give your cycle a clear name and describe its goals and objectives

Date Range

Set start and end dates to define the cycle duration

Status

Track cycle state: Backlog, Upcoming, Active, or Completed

Members

Assign team members who will participate in the cycle

Lead

Designate a cycle lead responsible for coordination

​
Cycle Status

Cycles progress through different states: 
const cycleStatuses = {
  backlog: "Planned but not yet scheduled",
  upcoming: "Scheduled to start soon",
  active: "Currently in progress",
  completed: "Finished and archived"
};
Only one cycle can be active at a time per project. Starting a new cycle will automatically move the previous active cycle to completed.

​
Active Cycle Dashboard

The active cycle view provides real-time insights:

​
Progress Tracking

Visual progress indicator showing work items closed vs. total work items:
- Completed issues (green)
- Started issues (yellow)
- Unstarted issues (gray)
- Backlog issues (light gray)
- Cancelled issues (red)

​
Burndown Charts

Visualize cycle progress over time:

Burndown Visualization

The burndown chart shows:
  • Ideal line: Expected progress trajectory
  • Actual line: Real progress against time
  • Work remaining: Issues or estimates left to complete
  • Scope changes: Issues added/removed during the cycle

​
Chart Types

Issue Count Burndown

Track the number of issues remaining over time

Estimate Burndown

Track story points or time estimates remaining

​
Managing Issues in Cycles

​
Adding Issues

Add work items to a cycle: 
// Three ways to add issues to cycles:
1. From issue modal: Select cycle in the cycle dropdown
2. Drag and drop: In cycle view, drag issues onto the cycle
3. Bulk operations: Select multiple issues and assign to cycle

​
Removing Issues

Issues can be removed from cycles at any time. Removed issues return to the project backlog.

​
Transfer Issues

When completing a cycle with unfinished work:
1

End Cycle

Click “End Cycle” on the active cycle dashboard
2

Transfer Incomplete Issues

Select incomplete issues to transfer to the next cycle or return to backlog
3

Complete Cycle

Confirm completion and archive the cycle

​
Cycle Analytics

Detailed insights available in the cycle sidebar:

​
Progress Statistics

- Issues assigned to each team member
- Completion rate per assignee
- Workload distribution
- Click to filter by assignee

​
Cycle Views

View cycle information in different layouts:

List View

See all cycles in a traditional list with key metrics and quick actions

Board View

Kanban-style board showing issues within the selected cycle

Gantt View

Timeline visualization showing cycle duration and overlaps

​
Cycle Filters

Filter cycles by:
  • Status: Active, Upcoming, Completed, Backlog
  • Date Range: Start date and end date filters
  • Members: Cycles by participant or lead

​
Archived Cycles

Completed cycles are automatically archived:
Archived cycles remain accessible for historical reference and analytics. View them in the “Archived Cycles” section.
// Access archived cycles
Project → Cycles → Archives

// Archived cycles include:
- All cycle metadata and settings
- Issue list (read-only)
- Final burndown and analytics
- Completion summary

​
Best Practices

Set Realistic Goals

Plan cycle capacity based on team velocity from previous cycles. Don’t overcommit.

Daily Progress Updates

Encourage team members to update issue states daily to maintain accurate burndown charts.

Regular Scope Review

Review cycle scope mid-sprint. Remove or defer work that won’t be completed.

Retrospective Analysis

Use archived cycle data to analyze team velocity and improve planning for future cycles.

Maintain Cycle Rhythm

Keep consistent cycle durations (e.g., 2 weeks) to establish predictable team rhythm.

​
Keyboard Shortcuts

ActionShortcut (Mac)Shortcut (Windows/Linux)
Create cycleQQ
View active cycleCmd+Shift+ACtrl+Shift+A

​
Code Example

Creating a cycle programmatically: 
const cycleData = {
  name: "Sprint 24 - Q1 Features",
  description: "Focus on user authentication and dashboard improvements",
  start_date: "2024-01-01",
  end_date: "2024-01-14",
  status: "upcoming",
  lead_id: "user-uuid",
  member_ids: ["user-uuid-1", "user-uuid-2", "user-uuid-3"]
};
  • Issues - Work items assigned to cycles
  • Modules - Feature-based grouping independent of cycles
  • Analytics - Detailed cycle performance metrics
  • Views - Custom views of cycle issues

Build docs developers (and LLMs) love

Get started for freeTalk to us