Skip to main content
Requirements Management using Jira

Link user stories and feature requests from Pivotal Tracker as requirements with test cases in TestCollab

Vishal Vaswani avatar
Written by Vishal Vaswani
Updated over 2 months ago

We often need test cases to be created around the user stories or feature requests in our project management system.

Requirements management feature of TestCollab lets you connect your Jira user stories to your Test Cases as requirements. Let us see how it works.

We would start by configuring the project specific settings to enable requirements management.

Requirements Settings

Administrators of a TestCollab instance can configure the settings to enable requirements management feature for a project using Requirements option under Settings menu.

Configuring Jira as a source of requirements in a TestCollab project

The next step involves selection of requirement manager, as on date of writing this, we support JIRA.

A JIRA account needs to be linked to fetch the issues from; please make sure that the JIRA user whose account is linked for the purpose has access to users, projects and issues.

Configuring Jira as a source of requirements in a TestCollab project

With a JIRA account connected, the administrator then configures settings further wherein he selects the JIRA instance, JIRA project and type of issues that would be linked as requirements with test cases.

Configuring Jira as a source of requirements in a TestCollab project

Once requirement configuration is done test cases can be linked with issues from JIRA instance.

Linking Requirements

Linking of requirements can be done by a user who has right to add or edit test cases in current TestCollab project.

When a user adds a new test case or edits an existing one, there would be an option of linking issues from JIRA as requirement.

Linking issues from Jira as requirements with test cases in TestCollab

Issues are fetched on the basis of search criteria entered by user, please note that the search would work on issue summaries (titles) as soon as the user clicks on "Search" button or presses 'Enter' or 'Return' key.

Please note that while searching the characters in the start of a word that is part of issue title would be considered. For example search string "test" would fetch "testing" but not "fastest".

Saving the test case would save new requirement also.

Viewing Requirements Linked with Test Case

When test case view is opened, a separate pane at the bottom lists the requirements linked with the test case.

Details of requirements linked with a test case in TestCollab

Requirements Page

There is a dedicated page that would list all the requirements linked with all test cases of a project.

On the page every requirement is linked to its source in JIRA and user also has option to get all the test cases shortlisted on basis of linked requirement when concerned column value is clicked upon.

Requirements used in a TestCollab project

Requirements Filter

As discussed above user can get the test cases shortlisted on the basis of linked requirement for this one can use the filters option on test cases page. Applying filter is straight forward one can select a criteria 'Contains', 'Not contains' and 'Is blank'. 'Is blank' can be used to see list of test cases that have not been linked with any requirement so far.

Filtering requirements in a TestCollab project

Bi-directional linking of requirements

You can get the bi-directional linking of requirements work if :

  • You have selected the same TestCollab project in JIRA for bi-directional linking as the one you have enabled requirements management for in TestCollab, and

  • You have also used the same JIRA project (to fetch issues from) to be linked as requirements

Let us now understand how bi-directional linking of requirements would work. Suppose you have linked an issue from JIRA as requirement with a test case in TestCollab, then in JIRA the same test case would also be shown as linked with the issue in JIRA.

Vice versa, if within JIRA you have linked one or more test cases with an issue then in TestCollab the same JIRA issue would be shown to have been linked with test cases as a requirement.

Traceability matrix for requirements

You can get a traceability matrix report generated for requirements in project to know :

  • Total number of requirements

  • Requirements covered (have test cases linked with them)

  • Uncovered requirements (having no test case associated)

  • Linked test cases count

TestCollab supports JQL syntax for issue search from Jira

Requirements traceability matrix for a project in TestCollab

Please see the user guide article that explains the report in detail

Did this answer your question?