There are times when an issue is related in some manner to another issue. The relationship generally is of the dependency type. In these cases, a user can relate two issues together to reflect such dependency. The application implements appropriate logic to enforce the rules of dependency between the two related issues.
There are three types of relationships:
- Related Issues:
In this case, two issues are just related to each other. There is no rule enforcement. The life cycles of the two related issues are independent of each other. For example, two similar issues may be related in this manner to allow users to view one issue while viewing the other issue also.
In this relationship, one of the two issues includes the other issue as its sub issue. A parent issue may include many sub issues as its child issues. But a child issue may have only one parent issue. In addition, the application enforces an issue life cycle rule: A parent issue may not be closed until all its child issues have been closed. For example, the user receives a report listing a number of defects found in the QA processes. The report may be entered as a parent issue and each defect in the report as a child issue. In this example, the report issue cannot be closed until all its listed defects are closed.
In this case, two issues are replicas of each other. They can be linked with this relationship.
Issue link relationships can be added and deleted in this tab. Current relationships of the selected issue can also be viewed in this tab.
Click on to add an issue. Issues can be linked to the selected issue either by typing its issue number or clicking on the Search button to the right and selecting the linked issue from the list displayed.