Versions Compared

Old Version 5

changes.mady.by.user Angelica Salazar

Saved on

compared with

New Version 6

changes.mady.by.user Angelica Salazar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Improved content
Info

In case of restricted user access you need the "Suspect Configuration" permission for the project, to access the suspect configuration. See Managing User Permissions for further information.

To use Suspects you just need to specify what issue fields should be monitored for changes and what kind of link types you want to be highlighted.

Configuring Suspects

...

Overview

Changes in a requirement may create a need to review related requirements, either requirements that refer to the changed requirement (upstream requirements) or requirements that it refers to (downstream requirements). 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, the scope of a change (i.e. whether it affects upstream or downstream requirements and which link types are to be examined) and the users that are to be notified when suspects are discovered.

Table of Contents

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

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.

Info

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

  1. Assignees: All assignees of linked issues matching the suspect configuration will receive a notification
  2. Reporter: The reporters of linked issues matching the suspect configuration will receive a notification
  3. Project Lead: The project lead of linked issues matching the suspect configuration will receive a notification
  4. Select specific users to receive a notification when a suspect is triggered

...

  • . 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.