Projects

A Project groups related tasks around a shared outcome. Tasks remain the place where execution, comments, status changes, and Agent runs occur; the Project provides the larger goal, ownership, progress, and cross-task context.

Projects belong to an Organization and can be associated with multiple Spaces.

When to use a Project

Create a Project when several tasks contribute to one outcome and need to be reviewed together, for example:

A product launch.

A customer delivery.

A reliability improvement.

A documentation rollout.

A cross-Space initiative.

Use a Sprint instead when the primary question is what should be completed in a particular time box. Use a View when the primary question is how to filter and display tasks.

Project properties

A Project includes:

Name and description for the outcome and scope.

Status: Backlog, Planned, In Progress, Completed, or Canceled.

Priority: Urgent, High, Medium, Low, or No priority.

Owner: an optional person or Agent responsible for the Project.

Spaces: one or more associated Spaces.

Labels for Project classification.

Tasks linked to the Project.

Progress derived from task status categories and, when used, estimates.

A Project owner coordinates the outcome; task assignees remain responsible for individual tasks.

Spaces and the primary Space

A Project is associated with one or more Spaces. One associated Space is selected as its primary Space.

The primary Space gives the Project a main organizational home. Additional Spaces let one Project include work from several areas of the Organization.

You can:

Add another Space to the Project.

Make an associated Space primary.

Remove an associated Space while at least one remains.

In the Project's Space management flow, removing the primary Space promotes another associated Space. Removing the last associated Space is not allowed.

Project access follows the Spaces a person can access. Associating a Private Space does not grant its contents to People who are not members of that Space.

Add tasks to a Project

A task can belong to one Project or no Project. The task still belongs to exactly one Space.

A cross-Space Project can therefore contain tasks from different Spaces while each task keeps its own identifier, task type, Workflow, labels, and access boundary.

Track progress

Project progress is calculated from the current tasks linked to the Project. The Project detail can show:

Total task count.

Counts by task status category.

Scope and completed estimate points when estimates are used.

Breakdowns by assignee or label.

Scheduled tasks in a Timeline based on start and due dates.

Keep task statuses and estimates current if the Project summary is used for planning or review.

Project status versus task status

Project status describes the overall outcome. Task statuses describe individual work items and come from each task type's Workflow.

Completing a Project does not replace the need to update its tasks. Likewise, one completed task does not automatically complete the Project.

Delete a Project

Deleting a Project removes the Project and unlinks its tasks. The tasks remain in their Spaces with their comments, history, and other properties intact.

Before deleting, confirm that the Project is not the only place where the outcome, scope, or decision history is explained.

When to use a Project#

Project properties#

Spaces and the primary Space#

Add tasks to a Project#

Track progress#

Project status versus task status#