R4J allows you to use Jira issue links to define the relationships and dependencies between requirements or other types of issues. When one requirement depends on another requirement, it can be useful to know when the requirement changes, since that may require corresponding changes in the dependent requirement.
R4J introduces the concept of suspect links to help you spot such cases and take appropriate action. R4J automatically monitors changes in your requirements and flags linked issues as "suspect" in order to identify them for review. This feature allows users to change requirements and then determine which other requirements might be affected by the changes. After review, the suspect flag can be removed.
Suspect links are identified in the following ways:
The Suspect Report (see below) provides a list of suspect links in a given project.
They appear in the affected requirements' Detail view in the section "Issue Links".
To create a Suspect Report, select Requirements > Suspect Report from the main navigation bar, select the relevant project and the “Go” button. The report is a table with a row for every suspect link. The Search field can be used to search the report for rows containing a given piece of text.
Include links to other projects
Include cross-project links flagged as suspect.
Restrict to issues with suspect flags created within the specified time period.
Restrict to specified link types.
The link type name is used to specify the link type (e.g. “trace”), while in the report the link description is used (e.g. “trace to”).
Restrict to changes made by the specified users.
The issue whose change triggered a suspect rule.
The dependent issue that might be affected by the change.
The link type between the changed issue and the dependent issue.
The user who made the change.
The date and time of the change.
Provides the following actions:
Compare the differences between the two issues.
Review the exact change that triggered a suspect rule.