Skip to main content

Projects

A Project is the top-level organisational unit in the PPM module. Work items can be grouped under a project, though this is optional — standalone and cross-project work items are also supported. Each project carries its own metadata, membership, and configuration.

Project metadata​

Each project holds information that applies to the entire body of work it contains:

  • Project manager — the user responsible for delivery of the project
  • Working calendar and hours — used for scheduling calculations across all work items in the project
  • Budget fields — reserved for cost tracking
  • Key prefix — a short code (e.g. WEB) used to generate human-readable work item identifiers like WEB-1, WEB-2

Projects and work items​

Projects and work items are stored separately. The project record holds project-level data (manager, calendar, budget, key prefix, membership), while the work item record holds task-level data (type, status, assignee, parent, dates, effort).

A work item's project_id links it to its project when one is set, and is left null for standalone items. Project membership and roles are managed independently from work item assignment — being assigned a work item does not imply project membership, and being a project member does not imply assignment to any specific item.

Membership​

A project has its own membership list. Each member is assigned a project-level role that determines what they can do within the project. See Role Hierarchy for the available roles and what each one can do.