Adding Associations and Dependencies
You can associate tracker issues with other tracker issues, forum topics, documents, source files, commits or external URLs. For example, an association enables you to define relationships between project plan documents and requirements, tasks or bugs.
To create an association:
1. Click Associations tab and select Add Association. The Creating new association window opens
2. Enter the required details.
3. Click Add.
A new association with the selected tracker is created.
 |
If an association is formed, you can add a comment for the association in the Comment field below the association definition and above the attachment selection. This comment is applicable to the association and not the whole issue. The text is only stored and displayed again if an association is formed.
|
Using the Association Settings Window you can associate the following artifacts
• History artifacts from your recent activities.
• Search results from the search tab.
• URL.
You can associate the following artifact types:
• Tracker Issues
• Source Files
• Documents
• Dashboard / Wiki pages
• Codebeamer internal or external URLs with maximum 4,000 characters
The association type can be:
• depends on
• superordinate to
• subordinate to
• related to
• derived from
• violates
• excludes
• invalidates
• copied from
Select Current HEAD from Baselines list, if you want that the association must belong to the last version of the item. You can also use Propagate suspects with Bi-directional or reverse direction.
Select the check box of a document, tracker issue, URL, forum topic or source file to be associated. Add a comment then click Add to add the new association. If a related-type issue association has formed, it will appear under the Related Issues tab in the details of the issue.
However, selecting a association-type of parent, child, or depends does not change any of the Children tab contents in any of the associated issues. Instead, use the Children tab to define dependencies.