Projects API

A project is one client engagement from discovery to maintenance: the container every component, environment, epic, story, requirement, test, release and incident lives under. It carries a short key (CRM) that prefixes every reference in it (CRM-142), a lifecycle status, the methodology it is run with, its visibility within the team, its four leads and its dates.

The reads here see the registry as the token sees it: every project of the team with visibility: team, plus the ones the person holds a membership row on, narrowed further by the token's scope:project: entries. A project outside that set is a 404 RESOURCE_NOT_FOUND, never a 403, so the API cannot be used to learn that a project exists. Every write runs the same action the registry page runs, under the same permissions (the team owner, then the person's project role, then their team role), and announces itself as a project.* event.

EndpointsCopy Anchor Link

Related

Clients APIThe organisation a project is done for.Teams APIThe tenant a project belongs to.Team Members APIInviting a client guest onto one project.Activity APIWhat changed on a project and who did it.project.* eventsThe lifecycle of a project and its membership: creation, edits, status moves, archiving, restoring, deletion, and people joining or leaving it.