DATA CENTER AND SERVER | CLOUD

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

The Suspect Concept

With R4J you can structure your requirements/issues with issue links. This allows you to clearly define the relationships and dependencies between requirements.

Suspects take this concept of dependency management one step further. They bring in the functionality to monitor changes in your issues automatically and mark their direct relationships "suspect" to identify them for review. This allows you to change your requirements and immediately know what other issues might be affected by the changes you made.

You can display the identified issues either in the issue detail view in the section "Issue Links" as textual and graphical representation, in the coverage and traceability matrix or as suspect report. It's also possible to search for identified issues with the advanced search functionality.

To configure the suspect triggers see Configuring the Suspect Logic.

Generating a Suspect Report

  1. Select Requirements > Suspect Report from the main navigation bar
  2. Select the relevant project
  3. Optional: Configure filters to apply on the report:
    1. Include links to other projects: if checked the report will also contain relationships to and from issues of different JIRA projects
    2. Period: if checked the report will only contain suspects whose timestamp is within the specified time period
    3. Link type(s): if checked the report will only contain suspects whose link type matches one of the specified types
      (lightbulb) Selecting "All Types" is the same as not using the "Link Type"-filter at all
    4. User: if checked the report will only contain suspects whose modifier of the changed issue matches one of the specified users
  4. Click on the Go button to generate the report

What information does the Suspect Report contain?

The suspect report consists of a table with the following columns:

Changed Issue

The changed issue that triggered the suspect.

Contains the project id (linked to the issue in the project tree or issue navigator), the summary of the issue that changed and the revision for every suspect.

(info) The table will contain a separate row for every relationship of a changed issue marked as suspect.

Linked Issue

The linked issue that might be affected by the changes.

Contains  the project id (linked to the issue in the project tree or issue navigator), the summary of the linked issue and the revision for every suspect link.

Link Type(s)

The link type between the changed issue and the linked issue.

User

The user who made the changes that triggered the suspect.

Suspect Timestamp

The date and time the suspect was triggered.

Action

Contains three buttons to either compare/review the changed issue and the linked issue or to clear the suspect.

Working with the Suspect Report

Search the report

To search the report for specific suspects click into the Search field located at the upper right corner of the report. It is possible to search for every entity of the report except for the available actions.

Compare Changed and Linked Issue

The Compare button at the end of every table row brings up a dialog to compare the changed issue against the linked issue.

Review Changed Issue

The Review button at the end of every table row brings up a dialog to compare the revision of the issue caused the suspect entry against the revision before.

Clear Suspect

The Clear button at the end of every table row allows you to remove the suspect mark from the corresponding relationship.

  • No labels