Versions Compared

Version Old Version 9 New Version Current
Changes made by

Angelica Salazar

David Sedlock

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: REQ-20552
Section Column
width70%
Integrity Checker

Overview

Since

R4J

easeRequirements extends the Data Model of Jira it also comes with an additional integrity checker.

The integrity checker searches for common data inconsistencies in the

R4J

easeRequirements data and attempts to keep the data in a consistent state. It also comes with a repair function which, in case of errors, attempts to reset the data to a stable state.

column
Table of Contents
width
minLevel
30%
1
Panel

On this page:

Table of Contentsindent15px
maxLevel7

Performing Integrity Checks

  1. Navigate to the Integrity checker page.

    1. Login as Jira Administrator.

    2. Choose 

Image Removed> Add-onsSelect R4J - Requirements Management for Jira > Integrity Check from the sidebar
(info) Keyboard shortcut 'g' + 'g' + start typing 'Integrity Check'

    1. Cog icon > Manage apps.

    2. Select easeRequirements > Integrity Checker from the sidebar.

  2. Select one or more items whose data you would like to check the integrity of

Click

  1. .
    (question) If executing the integrity check after an upgrade, “Select all“ is recommended.

  2. At the bottom of the page, select the Check button to

perform

  1. execute the integrity check.

After

  1. Once the integrity checker

run

  1. has finished processing, the result

of the check

  1. will be shown.
    The result contains passed test as well as information about the found inconsistencies

.
In case any inconsistencies were found during the run then R4J can attempt to correct them and bring your data to a stable state again. 
To initiate the correction select any inconsistencies you would like to correct and click the Fix button. 
(warning) Important

  1. .

    1. If all checks passed, proceed to the next step.

    2. If there are failed results, select the Fix button to correct the inconsistencies.

There are other integrity checks available but are typically only ran when issues in the specific area is encountered that cannot be fixed by the General checks.

  1. Find Duplicate Tree Items - run when there are errors or inconsistencies in a specific project tree.

  2. Find Invalid Baseline Revisions - run when there are errors or inconsistencies in a specific project’s baselines.

  3. Find References of Deleted Project(s) - run when there have been projects deleted in the instance to avoid failures on pages with data associated to the deleted projects.

Repeat steps 3 and 4 when executing these integrity checks.

Note

Important: It is strongly recommended taking a backup before trying to correct any inconsistencies.
If you chose to correct any inconsistencies, you will be presented with the result of the actions that have taken place.

Available Integrity Checks

General

Check Folder & Issue References

  • Check for issues that have been added to a folder but do not exist anymore

  • Check for parent issue and child issue references

  • Check for discrepancies in folder references

  • Check for discrepancies in requirement paths

  • Check for discrepancies in project tree structure

Check Add-on Configuration

  • Check revision blacklist for fields

that are unsupported or have

  • that are unsupported or have been deleted

  • Check reuse configurations for fields and link types that have been deleted

  • Check suspect configurations for projects and fields that have been deleted

  • Check baselines and issue revision history for projects that have been deleted

  • Check project categories that have been deleted

Check Add-on Permissions

  • Check global permissions for groups and projects that have been deleted

  • Check project permissions for groups and projects that have been deleted

Check Suspect Links

  • Check for issue links that have been set to suspect but do not exist anymore

Check Automatic Issue Import Configurations

  • Check for automatic issue import configurations whose projects do not exists anymore

  • Check for automatic issue import configurations whose users do not exists anymore

  • Check for automatic issue import configurations that are non-existent in easeRequirements and Jira tables in the database

    Status
    colourGreen
    titleV4.20

Specific

Find Duplicate Tree Items

  • Check for issues that have been added to the same project more than once

Find Invalid Baseline Revisions

  • Checks for empty and inconsistent baseline revision history data that may result in discrepancies in baseline details display

Find References of Deleted

projects

Project(s)

  • Check for references of deleted projects across all

R4J

  • easeRequirements data