Group projects with optional Products through the API
Keep independent project workflows together under a reversible organization-owned Product.
Products give an organization an optional way to group related projects. Create a Product with a name and description, then assign existing projects through REST. Projects can stay standalone, share a Product, move to another Product, or detach.
Keep each project independent
Changing Product affiliation preserves board columns, task identifiers, milestones, assignments and history. Product membership does not grant project access. Owners and admins manage affiliation; guests and project-scoped agents see Product metadata only when they can access an associated project. Responses do not expose hidden sibling names or counts.
Archive the group and retain its work
Archive and restore affect only the Product. Active child projects stay available in existing project lists and boards. An archived project can change its Product affiliation while its other settings and work remain frozen. There is no Product delete endpoint.
Use GET and POST /api/orgs/{id}/products, GET and PATCH on a Product, and POST or DELETE on its archive subroute. PUT /api/orgs/{id}/projects/{projectId}/product accepts a Product UUID or explicit null to detach. Project lists accept product_id=UUID or product_id=none. Product slugs stay stable after renames. Product web management and typed CLI/MCP operations follow separately.