Module guide
Projects
Containers for tasks with health and portfolio rollups.
Overview
Every task belongs to a project. Projects carry status, owner, and start and end dates, and they are the natural join point for board columns, workload, health scoring, and portfolios.
Highlights
The capabilities worth knowing before you dive in.
- Project health score combines overdue, blocked, velocity, and recency signals
- Portfolio rollup averages member-project health
- Per-project saved views and custom board columns
- Soft-delete plus restore, so nothing vanishes accidentally
Important to know
Limits, permissions, and sharp edges to keep in mind.
- Archiving a project hides every task from default views but keeps the data queryable.
- Cross-project bulk operations go through Bulk Edit in the list surface.
How to use it
The primary workflow, start to finish.
- Create a project from Settings > Spaces > New project.
- Assign an owner and cycle to anchor it in the planning rhythm.
- Review health on /workload and portfolios for at-a-glance status.
FAQ
- What happens to the tasks when I archive a project?
- They are hidden from default views and remain queryable. Nothing is deleted, so a report or an export that reaches for the data still finds it, and restoring the project brings the tasks back into view.
- How is the project health score calculated?
- It combines four signals: overdue work, blocked work, velocity, and recency of activity. A portfolio rolls up by averaging the health of the projects in it, so one badly slipping project moves the portfolio less than it moves itself.
- How do I change many tasks across several projects at once?
- Use Bulk Edit on the list surface. Per-project screens act on one project by design, and the list is the place where a cross-project selection is possible.
Automate this module
Everything on this screen is scriptable. Drive it from the REST API, or let an AI agent run it through the MCP server.
Was this page helpful?