Cycle Types

A Cycle Type is a reusable template that defines a category of cycle — its name, icon, and icon color — and controls which projects can use it. Project members pick from available types when creating a cycle in their project, so the visual language and vocabulary stay consistent across teams.

What a cycle type defines

Name — the category label project members see and select (e.g., Sprint, Release, Iteration, Phase).
Icon — a visual symbol chosen from a built-in icon library. Makes cycle types easy to tell apart at a glance.
Icon color — the color applied to the icon, giving each type a distinct visual identity.
Project scope — which projects can create cycles of this type.

Creating a cycle type

Navigate to Admin → Cycles and click Add Cycle Type. The editor opens with two tabs.

CYCLE TYPE tab

Name (required) — up to 100 characters. Names must be unique within the workspace (case-insensitive). Use descriptive names that project members will immediately recognise, e.g., Sprint, Release, Iteration, Phase.
Icon (required) — click any icon in the picker to select it. The selected icon is highlighted with an accent color.
Icon color (required) — set alongside the icon picker. The color is applied to the icon everywhere the type appears in the product.

PROJECTS tab

Controls which projects can use this cycle type.

All projects (default) — the type is available in every project, including projects created in the future. No further selection is needed.
Selected projects only — only the projects you select can create cycles of this type. Use the search box to filter the project list. At least one project must be selected.

You can change project assignment at any time by editing the type — with one exception, covered under the default cycle type below.

Default cycle type

One Cycle Type per workspace can be marked as the default. When a project member opens the cycle composer, the default type is pre-selected in the Type pill — they can change it before creating the cycle.

To set a type as the default, click its default toggle in the cycle types list. The previous default is replaced automatically.
The default flag can only be set, not unset directly. To remove a default designation, mark a different type as default instead.
Custom types you add in Admin appear in the composer picker automatically — no code change is required on the project side.

Changing the default: Click the default toggle on the type you want to make the new default. The previous default is cleared automatically — there is always exactly one default in the workspace.

The default cycle type must apply to All projects. This is enforced in both directions, and it follows from what a default is for: every project pre-selects it in the composer, so a default that only some projects could use would leave the rest pre-selecting a type they are not allowed to create.

Editing the current default and switching it to Selected projects only is rejected when you save.

Turning the default toggle on for a Selected-projects type is rejected too — the toggle flips back.

Either way the message reads “Default milestone types must apply to all projects. Enable ‘apply to all projects’ before setting this type as default.” To scope today’s default to specific projects, make another All-projects type the default first, then edit the original.

Editing a cycle type

Click the edit (pencil) icon on any cycle type row to open the editor. All fields — name, icon, icon color, and project scope — are editable. Changes take effect immediately and are visible to project members the next time they open the cycle form.

Switching project scope from All projects to Selected projects only (or vice versa) updates project availability immediately. Existing cycles of this type are not affected. The one move that is refused is narrowing the workspace default.

Deleting a cycle type

Click the delete (trash) icon on a cycle type row and confirm to remove it. Deletion is permanent.

The default cycle type cannot be deleted. The delete button is disabled for the default type. To delete it, first mark another type as default, then return to delete the original.

In-use cycles are reassigned to the default. If the type you are deleting is currently used by cycles in any project, those cycles are automatically reassigned to the workspace's default cycle type. No cycle data is lost — only the type association changes.

Project assignment

Use project assignment to scope a cycle type to the teams that need it. Some examples:

A Sprint type used by all teams → set to All projects.
A Product Release type only relevant to the mobile team → set to Specific projects and select those projects.

Project members only see the cycle types assigned to their project in the composer Type picker, keeping the list relevant to their team.