Projects
Plan bounded deliverables with milestones, linked issues, and health updates.
Projects
A project is a bounded deliverable: a clear outcome, a timeline, and a set of issues that execute the work. Projects belong to a team and may link to an initiative and Key Results.
When to use a project
Use a project when:
- Work has a defined start and target date
- You need milestones to checkpoint progress
- Multiple issues roll up into one deliverable
- Stakeholders expect project updates (
On Track/At Risk/Off Track)
Use a single issue for one-off tasks. Use an initiative when several projects share one strategic outcome.
Project lifecycle
Typical states progress from planning through delivery to completion. Exact status names depend on workspace configuration; common patterns include:
- Planned — scoped but not started
- Active — in progress
- Paused — intentionally on hold
- Completed — delivered
- Canceled — will not ship
Mark completed projects Done (or your workspace equivalent) so portfolio views stay accurate.
See Milestones for checkpoint planning.
Structure
| Element | Purpose |
|---|---|
| Team | Owns the project and its issues |
| Initiative | Optional parent grouping across projects |
| Milestones | Checkpoints with their own target dates |
| Issues | Execution tasks linked to the project |
| Documents | Specs, RFCs, launch checklists |
| Updates | Health and narrative status for stakeholders |
Views
Open a project to switch between views (availability depends on context):
- Overview — summary, properties, updates
- Issues — filtered issue list for the project
- Board / Table / Timeline / Stats — layout options for planning and tracking
Workspace Projects lists all projects; each team's Projects link filters to that team.
Milestones
Milestones break a project into sequential or parallel checkpoints. Each milestone can have:
- A target date
- Linked issues due before the checkpoint
- Progress inferred from issue completion
Define milestones during setup — see Set up your team and Create projects.
Status updates
Active projects should receive regular status updates, even when healthy. Updates surface in portfolio and initiative roll-ups.
Include:
- Health state (
On Track,At Risk,Off Track) - Short narrative on progress, risks, and decisions
Templates
Project templates seed milestones, issues, and properties for recurring project shapes (launches, migrations, onboarding). See Project templates.
Permissions
Creating projects requires create permission on projects for the target team. Editing properties and updates requires update permission. Workspace admins configure defaults under Settings → Projects.
Next
Last updated on