Creating projects
Important: Instance administrators are the only users that can create projects.
Project Creation Methods
If you are an instance administrator, you can create projects using the following three methods:
- Create empty project
-
Note: Any project can be used as a template to create a new project.
- Import a project
The following table outlines the data that is included in the project, depending on the method you use to create the project:
Empty Project | Project from Template | Imported Project | |
---|---|---|---|
Artifact Types | Default Types Only | Yes | Yes |
Custom Properties | None | Yes | Yes |
Project Group Definitions (not the group members) |
None | Yes | Yes |
Project Roles | None | Yes | Yes |
Project Role Assignments | None | Yes | No |
Office Document Templates | None | Yes | Yes |
ALM Targets | None | Yes | Yes |
ALM Security | None | Yes | No |
Folders | None | Yes | Yes |
Artifacts (including description and all other property values), excluding Baseline and Review Artifacts | None | Yes | Yes |
Baseline and Review Artifacts | None | No | No |
Artifact Traces (within the project) | None | Yes | Yes |
Artifact Traces (cross-project) | None | Yes | No |
Artifact Comments | None | Yes | Yes |
Artifact File Attachments | None | Yes | Yes |
Artifact History | None | No | No |
Artifact List Saved Views | None | Yes | Yes |
Reuse Relationships (within project) | None | Yes | Yes |
Reuse Relationships (cross-project) | None | Yes | No |
Collections | None | No | No |
In summary, anything that references instance data (example: users, project role assignments, cross project data) is not exported, and therefore will not be preserved after importing the project. The artifact history is also not preserved.
Tasks
Creating a project from a template
Importing a Blueprint sample project