Details on the project-subproject relationship
Within certain parameters, you can build complicated hierarchies of projects and subprojects to organize work.
The project-to-subproject relationship has the following characteristics.
- Any project or request can be linked to another project with the same security policy.
- A project can have at most one parent project or program, but not both.
- A project can have an unlimited number of child projects.
- A project can have both a parent and child project. This option makes it possible to have an
n-level deep hierarchy for projects, such as: parent project, child project, grandchild
project.
However, a request cannot be a parent. Requests can be a child of projects only.
- 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 you copy a project that is either linked as child or parent, the new project is not linked.
- Metrics, budgets, and the workflow do not roll up from a child project to a parent project.