Requirements Traceability

Owned by Sanjay Sahani
Last updated: Sept 03, 2014
3 min read

The Requirements Traceability View

Requirements Traceability view shows a summary of the map of all Requirements of a Project versus

  • JIRA Issues, including the custom issue types.
  • Requirement dependencies
  • Documents and links to Requirements

A sample view is presented below:

This functionality is identical to the one available in Requirements Tab, as described here Attaching documents and links to Requirements.

Linking Requirements with Artifacts

Requirement Manager can link/unlink JIRA issues/bugs/tasks/custom issues with a given requirement and can check traceability in real time.

  • To link an artifact to a requirement, just click on the corresponding cell of that row. After that a panel will appear containing:
    • Linked Artifacts table showing artifacts linked with this requirement. To unlink an artifact, just click on .
    • Link New Artifacts table showing artifacts not linked with this requirement. To link an artifact, just click on , that artifact will be automatically moved to linked artifact table.
    • Filters within the Panel
      • For "Link New Artifacts", user has an option to select Unlinked Issues by using Other Filter > Isolated option.
      • Please note that the panel shows issues only of the type chosen. For example, if you clicked on Bugs, then only Bugs will be displayed.

  • Color coding of table cells is done according to the status of the artifacts.
    • Red Color: if number of ("Resolved" and "Closed") artifacts are less than 50% of total attributes associated with requirement.
    • Yellow Color: if number of ("Resolved" and "Closed") artifacts are more than 50% and less than 100% of total attributes associated with requirement.
    • Green Color: If all artifacts are either "Resolved" OR "Closed".

Filters and View setting

  • The system also provides filters to view
    • Baselines, inlcluding
      • Latest version of Requirements
      • All versions of Requirements
    • Requirements associated with specific Releases
      • Requirements not associated with a Release can be selected by choosing the option "???".
  • User can configure the columns to be displayed in the Traceability view
  • Using the filters provided in the column headers, users can now identify Requirements not associated with Test Cases OR A Specific type of Artifact. This is depicted in the following image:

When using filters in a hierarchical view, please note that:

  • If a parent is selected in the filtering process, it's children will be shown.
  • If a child is selected in the filtering process, it's ancestors will be automatically selected.

 

Data Export to PDF

Requirement traceability table can be exported to PDF by clicking icon on top right corner.

CSV Export and Import

Please refer to Export and Import of Traceability information

 

Â