Details on the project/subproject relationship

The project-to-subproject relationship has the following characteristics.

Any existing project or request (having the same security policy) can be linked to another project (requests can only be children, not parents).

A project can have at most one parent project or program, but not both.

A project can have an unlimited number of children projects.

A project can have both a parent and children; this makes it possible to have an n-level deep hierarchy for projects.

You cannot delete a project that is linked to either a parent or child; you must first remove all parent/child (and project/program) relationships before you can delete a project.

When copying a project that is either linked as child or parent, the new project is not linked.

Metrics, budgets, and workflow do not roll up from a child project to a parent project.