View record detail

Tricentis Vera contains a robust log of all Vera-related activities. It tracks details, transitions, electronic signatures, and route activities that occurred on the record itself. Users have the option to view or print a detailed report. Designated users can approve or reject within each section when applicable.

The record details vary by record type, but they will contain a Vera Details section, a source system section (e.g., Jira Details or qTest Details), and an Approval Route section.

Vera Details

The Vera Details section includes the record definition:

Attribute Description
System The record source system.
Record ID The record source system identifier is also a hyperlink back to the record in the source system.
Record Type The classification of the item in the Vera.
Item Type The classification of the item in the source system.
Revision Revision is an optional field by record type. When configured, the revision number starts at one. It is incremented when an approved record is revised.
Author The Author field is configured as the individual who routed the record for approval or by a field value on the source record. The area is not displayed if an author is not configured for a record type. If the Author field is configured for a record type, but left blank, it will display as Unknown.
Record Status

The standard Vera status of the record in the Vera workflow.

  • Routing for approval: record status when a record is routed for approval and the approval route status is In Progress.

  • Rejected: the record status when an approval task in the associated approval route was rejected and the approval route status is Rejected.

  • Approved: the record status when the approval tasks in an approval route are approved, and the approval route status is Complete.

  • Draft: the record status when an approved record is revised, and a new revision is created.
Domain Name The Vera domain associated with the source system project.

Source System Details

The Source System Details section is displayed below the Vera Details section. This section contains record-specific data fields from the source system. The fields displayed are based on individual configurations. These source system data fields are verified along with associated signatures. For more details, see Signature verification failure report.

Note: Source record fields stored in Vera can be modified by configuring the record management policy.

This section lists all the fields that Vera displays in the Jira Details section. If you want to change their order, configure the records management policy.

The following fields are displayed in the Jira Details section:

Fields Description
Issue Type Jira issue type.
Description Jira issue description.
Summary Jira issue summary.

Please keep in mind these limitations about HTML formatting and styles:

  • Vera displays the plain text from the source Jira record unless you configure the field for Jira wiki support.

  • For Xray user defined user lists, Vera displays the User ID.

    For example, 6242b67adb7e006aa388b4, not the username John Doe

This section lists all the fields that Vera displays in the qTest Details section. If you want to change their order, configure the records management policy.

The following fields are displayed in the qTest Details section.

Fields Description
Project Name Source record's qTest project name.
Project ID Source record's qTest project ID.
qTest Version ID qTest test case version ID.
Description qTest test case description.
Linked Defects Defects linked to qTest test case.
Attachments Attachments linked to qTest test case.
Step Name qTest test case step number.
Step Description qTest test case step description.
Expected Result qTest test case step expected result.
Attachments (Step) Attachments linked to qTest test case step.
Linked Defects (Step) Defects linked to qTest test case step.
Test Case ID qTest test case ID of test run.
Status (Test Run) qTest test run execution status.
Attachments (Test Run) Attachments linked to qTest test run.
Linked Defects (Test Run) Defects linked to qTest test run.
Execution Log Name qTest test execution log number.
Test Case Name Name of qTest test case used to create execution log.
Test Case Version qTest test case version used to develop execution log.
Status (Execution Log) qTest execution log execution status.
Executed Start qTest execution log start date and time.
Executed End qTest execution log end date and time.
Execution Log Notes qTest execution log comments.
Attachments (Execution Log) Attachments linked to qTest execution log.
Linked Defects (Execution Log) Defects linked to qTest execution log.
Actual Results qTest execution log step actual result.
Status (Execution Log Step) qTest execution log step actual execution status.
Executed qTest execution log step execution date and time.
Tester Person who executed the qTest log step. 
Linked Defects (Execution Log Step) Attachments linked to qTest execution log steps.
Step Attachments (Execution Log Step) Defects linked to qTest execution log steps.

When handling previously formatted source text, there can be minor discrepancies between the source display and the display in Vera. Please keep in mind these possible differences about HTML formatting and style you may encounter:

  • When data is copied from Microsoft Word into qTest, and the qTest item is routed for approval, Word formatting tags are displayed in the Vera record.  Although word tags are not visible in either Word or qTest, they are retained as part of the original source data inside of qTest. They are then rendered by Vera as part of the original source data that is passed via the qTest API.  For example: <o:p></o:p>.

  • When images are embedded in qTest, they are displayed in Vera as download links, not thumbnails.

  • Tables created directly in qTest using the editor are displayed in Vera as formatted columns and rows, but table outlines are not displayed.  qTest table outlines are not part of the HTML that is available via the qTest API and therefore cannot be rendered in Vera.

  • Some background styles are not available in print view. If background style is relevant to the detail or meaning of a test step value, users are advised to find another way to meaningfully represent the data.

  • Supported HTML tags are: <address>,<article>,<aside>, <blockquote>, <header>,<hgroup>, <footer>,<h1>, <h2>, <h3>, <h4>, <h5>, <h6>, <section>, <div>, <li>, <ol>, <p>, <pre>, <ul>, <a>, <b>, <br>, <cite>, <em>, <i>,<main>, <nav>, <s>, <span>, <strong>, <u>, <caption>, <col>, <colgroup>, <table>, <tbody>, <td>, <tfoot>, <th>, <thead>, <tr> <figcaption>, <figure>, <hr>, <abbr>, <bdi>, <bdo>, 'code', 'data', 'dfn', <kbd>, <mark>, <q>, <samp>, <small>, <sub>, <sup>, <time>, <var>, <wbr>, <nav>, <img>.

In general, where qTest either sanitizes or does not render HTML, Vera will handle this in one of the following ways:

  • If the raw HTML is available via the qTest API, we will display the raw HTML.

  • If the qTest API does not make the html available, we will show a blank step in Vera.

We provide support for some Jira wiki formatted field styling.

  • For records that were routed prior to Jira wiki markup support, limited styling has been added for headings, text-effects, links, lists, tables, and images. Unfortunately, there are some limitations to other areas of support, including anchor links, file links, and panels. This is due to the lack of styling information that can be obtained from the Jira API.

  • For newly routed records, support is generally broader than for previously routed records. For records routed after adoption of Vera 2024.1, additional support is provided for text formats, including colored text; text breaks, panels, and code blocks.

  • Support for all of the previously mentioned items may vary slightly between Jira Cloud and Jira Server/Datacenter. Again, this is due to the limitations on the extent of the styling information that is provided by the Jira API.

Supported wiki style tags are: eadings, bold, italics, citation, strikethrough, underlines, superscript, subscript, block quote, colored text, text breaks, hyperlinks, email links, Jira username links, numbered lists, bullet lists, images, attachments, tables, panels, and code blocks.

Specific items that are not supported are:

  • Notation tags. Jira permits users to enter style notations into wiki type fields, which is sometimes resolved into rendered text, and other times those notations are not resolved. This can result in inconsistent styling between Jira and the record in Vera, depending on the information that can be obtained through the Jira API. We recommend that you do not depend on notations for styling. If notations are used, we cannot guarantee that there will be a style match between Jira and Vera.

  • Embedded images are sometimes displayed as attachments instead of thumbnail images.

  • Emoji formatting in Jira wiki fields is not consistently available via the Jira API. We therefore recommend that you don't use emojis as a means of conveying information in the context of test artifacts, but rather rely on the written word.

Note that Jira wiki formatting support is not enabled by default. To enable Jira wiki formatting for a field, check out Support for Jira wiki markup.

Approval Route

The Approval Route section displays the approval route and approval tasks associated with the demonstrated Vera record. Approve and reject options are shown if there is a pending approval task and the user is authorized to complete the approval task. See Approve records and Reject records for more details.

The following fields are displayed in the approval route:

Fields Description
Name The approval route name is associated with the record status. 
Status (Approval Route)

The status of the approval route:

  • In Progress: approval route status when one or more approval tasks are pending approval. Approvers can complete approval tasks.

  • Stopped: approval route status when an approval task in the associated approval route is rejected.

  • Canceled: approval route status when the record author withdraws or cancels approval.

  • Complete: approval route status when all associated approval tasks are complete.
Level The approval route level is the approval order. The previous level approval tasks must be completed before starting the next level approval tasks. 
Approval Task Approval tasks represent the approval roles needed to approve the associated record. The approval task also determines the meaning of the signature.
Status

The status of the Vera approval task:

  • Pending: waiting for the approver to complete approval tasks.

  • Canceled: pending approval task is canceled when the approval route is canceled.

  • Not Started: waiting for previous approval route level completion.

  • Complete: approver completed approval task.
Reviewer This field contains the approval role on pending and not started approval tasks. The approver's full name and username are displayed on the completed and rejected approval tasks. 
Date The Date field indicates the date and time when the approval task was completed or rejected in UTC time.

Activity History

The Activity History section displays the events associated with the Vera record.  Each event includes the record values at the time of activity.

The following activities are captured in history:

Activity Description
Record created The initial creation of the record when it was routed for approval and created in Vera.
Route Started The record state is set to Routing for Approval. The approval route is created.
Electronic Signature An approval task is approved and completed.
Rejection The record state is set to Rejected Record.  
Transition to Rejected One or more approval tasks have been rejected. The record state is set to Rejected.
Record Updated The record updates on subsequent route for approval activities after the record is created.
Route Canceled The approval route is canceled or withdrawn. 
Transition to Approved The record state is set to Approve when the Approval Route is Complete.
Transition to Draft  An approved record is revised. A new revision of the Vera record is created with a draft state transition.
Transition to Superseded A revised record is approved, and the previously approved record status is set to Superseded.

For Jira Cloud, Vera will display the Jira User ID.

Example: ug:20b7f3dd-cf98-42b8-99a0-2e5872258a6c, not the username John Doe.

Approval Routes

The Approval Route section displays the event history associated with the demonstrated Vera record. The section displays every approval route created for this record when it was routed for approval.

The following fields are displayed in the Approval Route section:

Fields Description
Route The approval route name is associated with the record status.
Status (Approval Route) 

The status of the approval route:

  • In Progress: approval route status when one or more approval tasks are pending approval. Approvers can complete approval tasks.

  • Stopped: approval route status when an approval task in the associated approval route is rejected.

  • Canceled: approval route status when the record author withdraws or cancels approval.

  • Complete: approval route status when all associated approval tasks are complete.
Owner Route owner from the source system, the user who routed the test for approval started.
Started The Date field displays the date and time when the approval route was created in UTC. 
Ended The Date field indicates the date and time when the approval route was completed, stopped or canceled in UTC time. 
Approval Task Approval tasks represent the approval roles needed to approve the associated record.  The approval task also determines the meaning of signature status.
Status (Approval Task)

The status of the Vera approval task:

  • Pending: waiting for the approver to complete approval tasks.

  • Canceled: pending approval task is canceled when the approval route is canceled.

  • Not Started: waiting for previous approval route level completion.

  • Complete: approver completed approval task.
Reviewer This field contains the approval role on pending and not started approval tasks. The approver's full name and username are displayed on the completed and rejected approval tasks. 
Date The date field indicates the date and time when the approval task was completed or rejected in UTC time.

Revision History

The Revision History section displays if the record has revisions.

The following fields are displayed in the Revision History section:

Fields Description
Revision The Vera revision number. Other revisions are listed with hyperlinks for the record revision.
Status

The status of the record in the Vera workflow:

  • Routing for Approval: record status when a record is routed for approval and the approval route status is In Progress.

  • Rejected: the record status when an approval task in the associated approval route was rejected and the approval route status is Rejected.

  • Approved: the record status when the approval tasks in an approval route are approved and the approval route status is Complete.

  • Draft: the record status when an approved record is revised, and a new revision is created approval.
Approval Date The Date field displays the date and time when the approval task was completed in UTC time.

Note: The revision history tab will only appear if there is more than one revision.

Linked Records

The Linked Records tab displays a list of records linked to the current record. It enables a quick access to related artifacts such as test cases, execution results, or requirement records.

Each linked record shows its type, ID, and title. You can open linked records in a new browser tab by selecting their ID.

Print View (Record Detail Report)

The Print View section displays the details and history from Vera details, signatures, and source system details in the browser with an option to print or save to PDF. This print view displays the record detail report.

The Print View includes release information with a filter option: A Releases filter that lets you choose which releases to include in the printed output. This allows you to tailor the print view to show only the relevant release details. To access this feature, follow these steps:

  • Select Print View.

  • Expand the Releases filter panel.

  • Select Export or Print.

Details

The  Record Detail Report includes almost the same data as the Details page, but it's formatted to be printer-friendly. The print preview includes these details:

  • System

  • Record ID

  • Record Type

  • Item Type

  • Revision

  • Author

  • Record Status

The Domain field is not included on print view.

The Signatures section has two options:

  • Signatures required: If approval route is setup so that signatures are required, then this section will display approval levels and their current statuses, and approval dates.

  • Signatures not required: If approval route is setup so that signatures are not required, then this section will display approval route name, a message No signatures required for this record, and the date of approval.

  • Issue Type

  • Description

  • Summary

  • Project Name

  • Project ID

  • Description

  • Linked Defects

  • Attachments

  • Step Name

  • Step Description

  • Expected Result

  • Attachments (Step)

  • Linked Defects (Step)

  • Test Case ID

  • Status (Test Run)

  • Attachments (Test Run)

  • Linked Defects (Test Run)

  • Execution Log Name

  • Test Case Name

  • Test Case Version

  • Status (Execution Log)

  • Executed Start

  • Executed End

  • Execution Log Notes

  • Attachments (Execution Log)

  • Linked Defects (Execution Log)

  • Actual Results

  • Status (Execution Log Step)

  • Executed

  • Tester

  • Linked Defects (Execution Log Step)

  • Step Attachments (Execution Log Step)

Note: Along with these fields, under the system details (Jira/qTest Details) section there might be additional properties which are defined in the record management policy. These fields are dynamic and added by user.

A Rejection Details section will be visible only if the record has a rejection. This section will contain a table with the following information: rejection reason, full reviewer name with reviewer username, the meaning of the approval task, and the date/time in UTC format that the rejection occurred. The Rejection Details section will not display once a record is fully approved, even if it previously had a rejection, because it is considered resolved.

Attachments

Image attachments are displayed inline at their original upload size. Non-image attachments are indicated with hyperlinks to the attachment in Vera.

Print Preview Details of Record Detail Report

Upon clicking the Print button, a print preview will display with additional information not seen on the Print View page.

  • Timestamp of when the record detail report was generated.
  • Footer name for Vera record detail report.
  • URL to the Vera record. 
  • Page number out of total pages.
  • End of document marker.
  • Conditional watermark based on record status.
Vera status Record detail report watermark
Routing for Approval Draft
Rejected Rejected
Superseded Superseded
Approved Approved Vera records will not have a watermark on the record detail report.