Skip to main content
Iterations bundle jobs into themed delivery slices. Think of them as releases, milestones, or phases, whatever framing fits your project.

​
Creating an iteration

  1. Click the iteration panel icon in the header (or use the iteration dropdown)
  2. Click + Add iteration
  3. Give it a name: “MVP”, “Phase 1”, “June Release”, or whatever makes sense

​
Naming conventions

There are no rules, but some patterns work well:
  • Sequential: MVP, Phase 2, Phase 3
  • Thematic: “Onboarding”, “Payments”, “AI Features”
  • Time-based: “June Release”, “Q3”
  • Quality-based: “Alpha”, “Beta”, “GA”
Pick whatever helps you and your team understand what’s in scope.

​
The Later iteration

Every project comes with a Later iteration. It’s the inbox, unassigned jobs default here. You can’t delete it. During planning sessions, review Later and pull jobs into real iterations. Anything that stays in Later indefinitely is either not important enough to schedule or needs to be reconsidered.

​
Reordering

Drag iterations in the iteration panel to reorder them. The first active iteration is treated as the “current” one by the API and AI features.

​
Marking done

When an iteration’s work is complete, mark it as done. Done iterations are hidden from the dropdown and Delivery Map, keeping your view focused on active work. The jobs retain their iteration assignment for reference.