Skip to content

Projects 101

A project is the container that holds a body of work — its items, docs, whiteboards, files and integrations — inside one team.

Creating a project

  1. Open the team that should own the project.
  2. Click New Project.
  3. Choose a template or start blank.
  4. Name it after the outcome you want, and set start and end dates if you know them — the Timeline view has nothing to draw without them.

The eight views

Same work, eight lenses. Switch with the tabs at the top of the project.

Overview

The project home: what changed, what is blocked, who is on what.

Board

Kanban columns by status. The daily driver for work in flight.

Backlog

Everything not yet scheduled, ordered by priority. Where triage happens.

Timeline

Dated work laid against the calendar — what ships this quarter, and what is slipping.

Calendar

Due dates and events by day. Good for load-balancing a week.

Tasks

A flat, filterable list of every work item. The one to use when you need to bulk-edit.

Files

Everything attached to the project and its work items, in one place.

Integrations

The project’s GitHub links, automations and connected tools.

The Timeline view has a page of its own: Timeline view.

Project status

A project carries one status, set by a person:

  • Active:Work is ongoing. The default.
  • Completed:The goal was met. Kept visible and searchable.
  • Archived:Out of the way but intact — data preserved and still searchable.

“At risk” is a health signal, not a status

Project health is computed from completion rate, overdue items and blockers, and reported as excellent / good / at risk / critical in analytics and on the Timeline. You do not set it by hand — it moves when the underlying work moves.

Sharing a project outside the team

A project can be published at an unguessable public URL that needs no login, with an optional expiry, and revoked at any time. The public view exposes only the project's name, description, status and dates plus each work item's title, status, priority and due date — never member emails or internal ids. Publishing is restricted to a workspace owner, an admin, or the project's creator. See Guests & sharing.

Deleting a project

Deleting a project is a 30-day soft delete, not an immediate cascade. The project and the work items that go down with it leave every view and become restorable from the Trash; after 30 days a scheduled sweep purges them permanently. Restoring the project brings back exactly the items that were deleted alongside it, leaving anything you had already deleted separately in the Trash. See Trash & restore.