Skip to main content
Projects group issues under a named delivery track. When a collection of issues needs its own lane, owner, and status instead of living as unrelated work, create a project.

​
When to use a project

Use a project when:
  • a set of issues shares a delivery goal and should move together
  • the board needs to track progress at a level above individual issues
  • issues need a named owner and a target date
Do not create a project for every issue. Projects add structure — use them when that structure is actually useful.

​
What the list shows

Each row in the project list shows:
  • project name
  • description
  • target date (if set)
  • current status

​
Project detail

A project detail page has two sections: Overview — the project’s issues, their current states, and overall progress toward the project’s status. This is where the board checks how a delivery track is moving. Configuration — the project name, description, owner, target date, and status. Edit these here when the project scope or timeline changes.

​
Issue assignment

An issue can belong to one project at a time. To assign an issue to a project, open the issue detail and set the project field there. Issues that belong to a project still appear in the main Issues list. The project grouping adds context — it does not remove the issue from the global work list.

​
Status

Project status is independent from issue status. The values are: backlog, planned, in_progress, completed, cancelled. Move a project to completed when all its issues are done and the delivery track is closed. Status is set manually — it does not update automatically based on issue states.
  • Initiatives — planning layer above projects
  • Issues — the individual work items inside a project