DATA CENTER AND SERVER | CLOUD

Configuring Suspect Logic

Overview

Changes in a requirement may create a need to review linked requirements (or other types of issues) that depend on it. R4J allows you to create a fine-grained “suspect logic” that alerts users to requirements that need review due to changes in linked requirements. The logic takes the form of project-specific rules that specify which fields are to be monitored for changes, which link types are to be examined, and the users that are to be notified when suspects are discovered.

Configuration of Suspect Logic Rules

To configure rules for suspect logic, you need the "Suspect Configuration" user permission - see Managing User Permissions.

In the Jira main navigation bar, select Requirements > Suspect Configuration. Selecting the desired project causes the existing rules for that project (if any) to be displayed. The following actions are available:

Purpose

Action

Purpose

Action

Create rule

Select the option Add Suspect Configuration.

  • Give the rule a name.

  • Select the fields you want to be monitored for changes. Choose <All fields> if you want all fields to be monitored.

To avoid being overwhelmed by requirements incorrectly getting marked as suspect, think carefully about which fields are selected here. Only those fields that, if changed, might necessitate changes in related requirements should be included. The requirement description is an obvious candidate, since a change in a requirement’s description may necessitate coordinated changes in the descriptions of related requirements. But a change in, say, the assignee of a requirement probably has no impact on related requirements.

  • Select the link types you want to be included in the scope of the rule. Choose All Types if you want all types of links to be included in the scope.

  • Select whether the scope includes only downstream relationships (i.e outgoing links), upstream relationships (i.e incoming links), or both.

  • Optionally select specific users or roles that receive a notification when a requirement is marked as suspect. The possible roles are assignee, reporter, project lead.

  • Select Add to create the rule, which takes immediate effect.

Modify rule

Select the edit icon next to the rule, modify the rule configuration as desired and select Update.

Delete rule

Select the delete icon next to rule and select Delete.

Linked Issues as trigger for suspects

There may be a need for requirements to mark newly linked issues as suspects to check its impact on requirements. When linking an existing issue or creating a new link, regardless of the scope indicated, the link between both changed and linked issue will be marked as a suspect since it is identified equally as a change for both.

The revision may also show the issue keys in the “R4J Suspect“ revision interchangeably (in the example below, ABC-123 and ABC-456) since Jira does not provide the direction which the links are created.
Example of an “R4J Suspect“ revision: R4J Suspect: Suspect set in ABC-123 due to change in ABC-456