Setting up traceability between ACCELQ Scenarios and Requirements in external systems

When you write a Scenario in ACCELQ (both Automation and Manual), you can set up traceability with application Requirements that are managed in external systems. ACCELQ currently supports following Requirements/Bug tracking systems:

• Jira On-Prem and Jira Cloud
• Azure/TFS
• Rally Cloud

Requirements traceability allows you to:

• Build dynamic Test Suites in ACCELQ that cater towards a given Sprint or Release (defined by a set of Requirements). Here is more information about Requirements based suite.
• Show test coverage information in Jira or Azure against the Stories (or work items). Dev and Project teams get access to this test coverage information without leaving the Requirements management platform, along with an ability to navigate to the Scenario in ACCELQ. This functionality requires deploying ACCELQ-Connect plugin on Jira/Azure. Here is a detailed article for Azure and Jira

Configuring the connection with the external system

Before you can link a Scenario with the external system, you need to set up connection information in the Project Configuration screen. You need Project Admin privilege for this setup.

Here is an article with detailed steps involved in configuring this connection.

Linking Scenario with a Requirement

When creating a Scenario, you can switch to Traceability tab and search for the Items in the configured external system. You can either type Item Key or Title/Summary to search.  

You can also review and edit this traceability once the Scenario is created.

Traceability information in external systems

In addition to pulling information from external systems to ACCELQ, you can also review this traceability information directly in the external systems. This is achieved using plugins for Jira and Azure. Here is an article detailing this setup.