Relationships help users find all of the assets that they need to complete their tasks. A list of related assets appears on the General Details page of an asset. In the Eclipse client, when you import an asset you will be prompted to download any related assets at the same time. You can use the Visual Browse tool to see a graphical representation of assets and their relationships.
Repository administrators can create additional relationship types that fit the needs of their organization. For example, if the organization produces assets that must be tested, the repository administrator can create a relationship type called test.
To provide governance, repository administrators can place relationship constraints on an asset type. The repository administrator can require that users who submit an asset of a certain type also include assets of a certain relationship. For example, if an organization produces assets that must be tested, the repository administrator can create a constraint on an asset type so that users must include a related testing asset along with an asset.
Users can specify that a relationship only exists for a specific asset version or range of versions.
| Relationship | Reverse relationship |
|---|---|
| Parent | Child |
| Dependency | Dependent |
| Implementation | Specification |
| Test | Test for |
| Tutorial | Tutorial for |