Plan issues in cycles

A cycle is a dated planning period for a team's issues, numbered Cycle 1, Cycle 2 and so on. Cycles are off until a team admin turns them on.

Turn cycle planning on

A team admin opens Statuses, then Manage cycles under Cycle planning, and turns the setting on. Cycles then appears in the More menu on the Issues page, and a Cycle choice appears on the issue edit page and in the bar for changing many issues. Members who can edit issues can then create cycles.

Turning cycle planning off keeps the existing cycles and their issues, and hides them until it is turned on again.

Create a cycle

On Cycles, choose Create cycle. Choose the start date and a length of 1 week, 2 weeks or Custom. A custom cycle also needs an end date, and the end date is part of the cycle. Two cycles in a team cannot overlap.

A cycle's dates cannot be changed after it is created, and a cycle cannot be removed.

Add issues to a cycle

On an issue, choose More, then Edit labels, milestone and other fields, choose the cycle and Save cycle. To move several issues, select them on the Issues list and choose Cycle in the bar above the list (see Issue list, board and saved views).

Issues stay in their cycle when it ends. To carry unfinished work into the next cycle, select those issues and choose the next cycle.

Follow a cycle

Cycles lists every cycle, newest first, with its dates and how many of its issues are completed. A cycle's page shows how many issues are Completed, In progress and Remaining, then its issues grouped by status. In progress counts statuses in the Started category; Remaining counts the Backlog and Unstarted categories (see Issue statuses, custom fields and automations). An issue page shows its cycle while cycle planning is on.

For help with cycles, Contact support.