Record Integrity

Record Integrity monitors records that Vera approves in connected source systems. When Vera approves a record but the source system doesn't reflect that approval, Vera automatically logs a sync issue. The Record Integrity page is your central workspace for reviewing, investigating, and resolving those issues.

Record Integrity supports Jira and qTest source systems.

Before you start

To use Record Integrity, you need to be a Site Administrator.

To define who receives email alerts, configure the settings on the Mismatch Notification page.

Open the Record Integrity queue

To open the queue, follow these steps:

  1. Go to the administration area.

  2. In the navigation menu, select Source Record Management.

  3. Select Record Integrity.

The queue opens with a default filter that shows only records with a triage status of Unreviewed or Confirmed Mismatch. Records that are already resolved or confirmed are hidden. To see the full history, clear the filter.

Queue columns

Each row in the queue represents one sync issue. By default, the queue shows the following columns:

Column

Description

Record name

The name of the Vera record.

Mismatch type

The category of the sync issue. The only mismatch type is Status, which means the record state in Vera doesn't match the state in the source system.

Triage status

The current review state of the sync issue. Check out Triage statuses.

Source system

The connected system where Vera detected the sync issue: Jira or qTest.

Timestamp

The date and time when Vera first detected the sync issue.

Occurrences

The number of times Vera has detected the same sync issue for this record.

Record ID

The internal Vera identifier. Hidden by default.

Source system ID

The corresponding identifier in Jira or qTest. Hidden by default.

To focus on a specific set of records, filter the queue by source system, mismatch type, triage status, or approval date range.

Triage statuses

Each sync issue has one of the following triage statuses:

Status

Meaning

Set by

Unreviewed

Vera has detected a sync issue, and no action has been taken. All new sync issues start here.

Vera

Confirmed Mismatch

A check confirmed that the Vera state and the source system state still don't match.

Vera, after a check

Confirmed Match

A check confirmed that the states now match. You don't need to do anything.

Vera, after a check

Resolved - dismissed

An administrator dismissed the issue and entered a reason. The record may reappear in the queue if Vera detects the same mismatch in the next check.

Administrator

Resolved - fixed

Auto-fix corrected the sync issue, or a check confirmed the record is now in sync after a manual fix.

Vera

Check a record

A check confirms whether a sync issue still exists by querying both Vera and the source system in real time. We recommend that you check every new record first, so you know whether the issue is still present before you decide how to resolve it.

To check one or more records, open the queue and select the records you're interested in. Then, select Check.

Vera checks each selected record, shows the Vera state and the source system state side by side, and updates the triage status based on the comparison.

If you run a bulk check, Vera displays a summary that shows how many records were confirmed as matches, how many were confirmed as sync issues, and how many failed to check because of an error such as an API timeout. Vera records each result in the record's audit history.

Dismiss a sync issue

Dismiss a sync issue when the mismatch is acceptable and doesn't require a correction to the source system. Dismissal is an administrative acknowledgment, not a technical fix.

Dismissal doesn't change the state in Jira or qTest. If the records still don't match, Vera detects the mismatch again on the next check, and the record reappears in the queue with an incremented occurrence count.

To dismiss a sync issue, follow these steps:

  1. Select one or more records with a triage status of Confirmed Mismatch.

  2. Select Dismiss.

  3. Enter a reason. Vera requires a reason and stores it permanently in the audit history.

  4. Select Confirm.

The triage status changes to Resolved - dismissed and Vera removes the record from the default queue view.

Auto-fix a sync issue

Auto-fix attempts to correct a sync issue by pushing the source system to the state that Vera expects. The behavior depends on the source system.

Run Auto-fix

To run Auto-fix, follow these steps:

  1. Select one or more records with a triage status of Confirmed Mismatch.

  2. Select Try to fix automatically.

  3. Confirm the prompt.

  4. Review the result. Records that Vera fixed move to Resolved - fixed. Records that Vera couldn't fix remain in Confirmed Mismatch, with the reason in the audit history.

For Jira, Vera looks for a workflow transition path from the record's current state to the required state:

  • If a valid path exists, Vera executes the transition automatically and the triage status updates to Resolved - fixed.

  • If no valid path exists, auto-fix fails and Vera shows the transitions available from the record's current state. Use that list to identify the missing transition, add it to the Jira workflow, and try auto-fix again.

For background on the required transitions, check out Integrate Vera workflow states into Jira workflows.

Auto-fix for qTest requires that the Vera service account has the necessary permissions in qTest.

For qTest, auto-fix runs a full remediation sequence that covers cases where the original approval call failed because of a timeout or connection error. Vera performs the following steps:

  1. Transitions the test case or test run to Approved in qTest.

  2. Cleans up the approval route to reflect the correct approver sequence.

  3. Executes the approval API push.

  4. For test cases only, marks the test as Approved in qTest, so that the test can be executed.

Add a status mapping

If your source system intentionally uses a different state than Vera expects, for example Released instead of Approved, add a status mapping so Vera stops flagging those records as sync issues. A status mapping tells Vera to treat a specific source system state as an acceptable match for a Vera workflow state. After you add a mapping, future checks no longer flag records in that source state as a sync issue for that workflow state.

A status mapping changes the workflow configuration. It applies to every record that goes through the affected workflow state, not just the record you're viewing. Confirm the change with your team before you add the mapping.

To add a status mapping, follow these steps:

  1. Select a record with a triage status of Confirmed Mismatch.

  2. Select Add status mapping.

  3. Select the source system status to accept as valid for the current Vera workflow state.

  4. Select Add.

The mapping is saved to the workflow configuration and the record triage status updates. To review or remove status mappings later, check out Manage workflows.

Export sync issue records

Export the queue to CSV to share sync issue data with your team, track resolution progress offline, or build an audit trail for compliance.

Export type

How to export

Selected records

Select one or more records, then select Export CSV.

Filtered view

Apply a filter, make no selection, then select Export CSV.

All records, including resolved and historical entries

Clear all filters, make no selection, then select Export CSV.

The CSV includes the ID, Record ID, Record name, Source system ID, Triage status, Mismatch type, Source system, and Timestamp for each exported record.

Audit history

Vera records every detection, check, dismissal, auto-fix, and status mapping in the audit history for the affected record. You can't edit or delete audit entries.

To open the audit history for a record, select the record in the queue and open the Audit history tab. For the audit history across all records, check out Audit History.

What's next

Now that you can triage sync issues, here's what you can do next: