Release Management

The release management feature in Vera allows you to track traceability from releases to requirements, test cases, and test runs. You can also explore record-specific associations in the Linked Records tab of any requirement, test case, or test run. This view lets you filter by release and see related records in the same release scope.

Before you start

When upgrading to a version of Vera that includes Release Management (2024.2 and later), keep the following behaviors in mind:

  • Newly created qTest test cases and test runs are imported into Vera as draft records.

  • Existing test cases and test runs—created before the upgrade—are only imported as drafts if updated in qTest.

  • Test cases automatically inherit the releases of their linked requirements or test runs.

  • Release status in Vera always appears as Planned.

  • Release workflows in Vera are not yet synced with Jira or qTest.

Set up the integrations

To set up a Jira-qTest integration or a qTest Requirement integration, follow the instructions:

Before using release management with Jira–qTest requirements, complete the following setup:

  • Update the Records Management Policy (RMP) in Vera to support the Jira–qTest Requirement record type.

  • In qTest:

    • Enable the Jira–qTest integration

    • Import Jira releases into qTest

    • Import Jira requirements into qTest

To enable traceability, follow this workflow:

  1. Create a Requirement issue in Jira. It automatically imports into qTest as a requirement.

  2. The qTest requirement is imported into Vera as a Jira–qTest Requirement in draft state.

  3. Route the requirement for approval. Once approved, Vera pulls full Jira details and applies the original record type.

  4. Vera imports the linked release at the same time as the requirement.

To complete traceability from requirement to test run, follow these steps:

  1. In Jira, add a fix version to your issue to define its release.

  2. In qTest, link a test case to the requirement. Vera automatically imports it as a draft.

  3. Route the test case for approval. It updates in Vera accordingly.

  4. In Vera, open the Linked Records tab of the requirement and select a release to view related records.

  5. In qTest, link a test run to the test case. Vera imports the test run as a draft, and updates it once routed.

Note: While a record is in draft state, Vera displays only basic details from qTest. Jira-specific data becomes visible only after approval.

To use release management with qTest-only requirements, you will need to update the RMP in Vera to support the qTest Requirement record type.

To enable release traceability, follow this workflow:

  1. Create a release in qTest.

  2. Create and link a requirement to the release. It is automatically imported into Vera with associated release metadata.

  3. In Vera, go to the Linked Records tab and select the appropriate release to view related records.

  4. Link a test case to the requirement. It is automatically imported into Vera.

  5. Route the test case through the approval process.

  6. Create and link a test run to the test case. It is imported into Vera and updated after approval.

Linked Records tab

You can use the Linked Records tab in Vera to explore all requirements, test cases, and test runs tied to a specific release.

The release dropdown behaves in two ways:

  • If the record is linked to a release, the dropdown filters only to relevant releases.

  • If the record has no linked release, the dropdown displays all releases for the domain.

Note: qTest releases are only imported into Vera when related items—requirements, test cases, or test runs—are routed.