Managing custom artifact types

Overview

Project administrators with the correct privileges can create custom artifact types at the project level to meet the needs of the project. Each custom artifact type must have a unique ID prefix and must be associated with one of the pre-configured base types. Custom artifact types provide you with an extremely large amount of flexibility in the way you categorize the artifacts in your projects.

Example

Tyler, a business analyst, is configuring a new project which involves the creation of a large number of business and functional requirements in textual form. He wants to ensure there is a high level of visibility between business and functional requirements.

He considered adding a custom property (with Business or Functional options) to the existing Textual Requirement artifact, but he feels it will not offer enough visibility.

Tyler decides to create two different artifact types called Business Requirements and Functional Requirements. He sets the Base Type to TextualRequirement for both of the new artifact types. Tyler deletes the existing Textual Requirement artifact type as it is no longer needed. Now, users must choose between a business requirement or a functional requirement when creating a new requirement.

Project administrators with the correct privileges can create and edit custom artifact types using the Custom Artifact Types tab in the Project Administration Console. The Custom Artifact Types tab looks like this:

The left side of the page provides you with a table containing the following columns of information about each artifact type:

After you select a custom artifact type from the table, the custom artifact type details are displayed on the right side of the page.

Tasks

Creating custom artifact types

Modifying custom artifact types

Deleting custom artifact types

Learn More

Managing custom properties

Project Administration