Reverse Traceability

Using RMsis,

• Requirement Manager can easily track requirements and test cases associated with a given JIRA artifact.
• It would also be possible to get a list of artifacts associated with a Release.

Artifact Attributes

An artifact has the following attributes:

• Jira Reference: This field specifies unique key (Jira reference id) of the artifact.
• Summary: This field specifies brief summary description of the artifact.
• Artifact Type: This field specifies type of the artifact. Artifact types are automatically synchronized with issue types in Jira.
• Priority: This field specifies priority of the artifact. Possible values are "Blocker", "Critical", "Major", "Minor" or "Trivial".
• Status : This field specifies status of the artifact. Possible values are "Open", "In Progress", "Reopened", "Resolved" or "Closed".
• Due Date : This field specifies the due date specified by Project Lead / Manager for the artifact.
• Assignee : This field specifies owner of this artifact.

• Reporter : This field specifies reporter of this artifact.

Artifact Links

• Requirements: This field shows the Requirement Id's, which are linked with this artifact.
• Test Cases : This column shows the Test Case Id's, which are linked with this artifact.
• JIRA Issues / Artifacts (Bug, New Feature, Task, etc.) : These columns show the JIRA issues / artifacts of corresponding type linked with this artifact.

Artifact Operations

The following operations can be performed:

• Add Artifact: An artifact can be created by clicking on "Add Artifact" button. A Jira issue panel will be opened to create a new Jira issue. Artifact table will be automatically updated after closing the Jira issue panel.
• Edit Artifact: An artifact can be edited by clicking in "Jira Reference" column. A Jira issue panel will be opened to edit that Jira issue. Artifact table will be automatically updated after closing the Jira issue panel.
• Link Requirements: An artifact can be linked to one or more requirements. A requirement can be linked to an artifact by clicking on "Requirements" column for an artifact row. After a panel appears, check on the requirement rows to link requirements.
• Quick Link:
  

  • This functionality has been provided to enable linking multiple entities with a JIRA issue/ artifact without having to select multiple check boxes in UI.

  • When you open the panel for linking requirements / test cases in the Reverse Traceability tab, a text box "Quick Link:" is available where you can type in entity-id for multiple entities (separated by comma) to be linked with a JIRA issue. (Please note that the complete entity id should be entered here, including the version number e.g. REQ-R1{1} ).

  • You can click on the “Link” button to link the entities with the JIRA issue.

• Link Test Cases : An artifact can be linked to one or more Test Cases. A Test Case can be linked to an artifact by clicking on "Test Cases" column for an artifact row. After a panel appears, check on the Test Cases rows to link them.
• Filters:
  
  • JIRA issues can be filtered on "Artifact Type", "Priority", "Assignee", "Reporter", "Requirements", "Test Cases" and "Status".
  • In order to get a list of issues associated with a release, a user can also choose the JIRA version from the drop-down list.
• Export (PDF/ CSV): JIRA issues can be exported to PDF/ CSV document by clicking icons shown on top right corner. 

Further reading