Linking artifacts in different projects or components
A link represents a relationship between artifacts. Link relationships are directional and indicated by an icon. Link types help you define and customize the linking relationships between artifacts. Each link type has an outgoing and an incoming role. You can create links between artifacts in different projects on the same server or on different servers. If you enable configuration management, you can create links between artifacts in different components.
Cross-project or cross-component linking is automatically enabled for system-defined link types. However, if link constraints are set the cross-project and cross-component linking is governed by the link constraint rules.
To enable cross-project or cross-component linking for a custom link type, a URI must be defined for the link type. For example, https://hostname.com/domain/myLabel. Define the same link type with the same URI for the projects or components that you want to link. To create link from both ends, see Creating RDF vocabulary documents and assigning URIs. If you enable cross-project or cross-component linking in only one project or component, but not in others, you can still create the link but only from the project or component where the link is defined. This is because the link direction for a cross-project or cross-component link determines where the link is stored. Cross-project or cross-component links are stored in the source artifact's project or component area. The outgoing role represents the source of the link. If you use link constraints, you must define equivalent URIs for the requirement types.
When viewed in the context of a local baseline, rich hovers for links to artifacts outside that baseline say that the artifact cannot be found in configuration. The Links sidebar section shows the links' information.
- The Link Index Provider (LDX) application must be installed and registered with the Jazz® Team Server.
- If you are using a topology with multiple Jazz Team Server (JTS) instances, you must set up bidirectional friend relationships between the Requirements Management (RM) servers, and between LDX and any RM servers that are running on a different Jazz Team Server than LDX.
- The data source for all RM servers must be added to LDX.
- All participating project areas must be enabled for configuration management.
- The user must be working in a global configuration context.
- Project areas that link to each other must be associated with the Related Requirements association on the Overview page for project area administration.
- You can view, create, modify, and delete cross-server links in both grid columns and the Links pane in the sidebar.
- When you hover over a cross-server link, information is displayed about the artifact at the other end of the link.
- You can use a drag-and-drop operation to create cross-server links.
- The reports that are generated when you export comma-separated value (CSV) files and spreadsheet files contain the cross-server links.
- Link validity is fully supported for cross-server links.
For a cross-project or cross-component link, the link direction determines where the link is stored. Cross-project or cross-component links are stored in the source artifact's project or component area. The Outgoing role represents the source of the link.
- Import CSV
- Link By Attribute
- Duplicate Artifact
- When you create a cross-component link to an artifact in a baseline component, the new link cannot be stored in the baseline component.
- When you create a link to the web, the new link is stored in IBM® Engineering Requirements Management DOORS® Next (DOORS Next).
- When you create a cross-component or cross-project link by using a link type that is only defined in one of the projects or components that are involved in the link, the new link must be stored in the project or component that defines the link type.
- When you Clone from Component only Outgoing links are cloned and stored in the source artifact.
- When you Copy from Component only Outgoing links are copied and stored in the source artifact.
Link direction and change sets
- If the other component that is involved in the link requires that all changes occur in changes sets, but a change set does not exist, the list of available link types is filtered to show only outgoing link types.
- If the other component that is involved in the link is using a change set, a warning message is displayed that explains that you must deliver the other component's change set after the link is created.
- If the specified link type is incoming, and you switch the component to one for which a change set is required but does not exist, an error is displayed and the list of available link types is filtered to show only the outgoing link types.
Editing existing cross-project or cross-component links
- If the link is incoming from an artifact in a component for which change sets are required, and no change sets exist, an error message is displayed that explains why you cannot edit that link.
- If the link is outgoing to an artifact in a component from which change sets are required, and no change sets exist, the list of available link types is filtered to show only outgoing links. A warning message is displayed that explains why you cannot specify an incoming link type.
- If you change an outgoing link to an incoming link, and the link originates in a component that is in a change set, a warning message is displayed that explains that you must deliver the change set to see the changes to the link.
- If you edit an incoming link, and the link originates in a component that is in a change set, a warning message is displayed that explains that you must deliver that change set to see the changes to the link.