Forum Discussion

renuvish's avatar
Occasional Contributor
4 years ago

Traceability report not including the epics


  It would be good if the traceability report shows the traceability from the epic till the defect. Currently it shows only from userstories in the tabular form. In our org we have the below structure

BRD documents in confluence 


      User stories

          Test cases (linked to User stories)

             Defects (linked to test cases)

So in the traceability report , we would like to see a table showing us right from epics all the way to the defects


Also we dont seem to have the backward traceabilty report from Defect to requirement. Zephyr for Jira has this capability. Would be nice if we were to have that here. Also the traceability direction currently shows only two direction (coverage to testcase and test case to coverage) and the link tod efects is not very clear. The traceability tree feature which is beta now does not seem to be very helpful for our usercase. 




4 Replies

  • deitahoward's avatar
    SmartBear Alumni (Retired)


    For the Traceability reports, if you're using the Cloud up, you're right - there isn't an option for seeing the traceability from the Epic level. 

    Zephyr Scale has an "Ideas Portal" that they review weekly, so you can head there and create one for this or vote on it if it already exists. Here's the link -

    For the Coverage report, you can actually filter it by Issue, which takes a Saved Filter from Jira and let's you see the reverse coverage (you can identify issues that don't have any test case covering). 

    That could be an option?



    • renuvish's avatar
      Occasional Contributor

      Hi deitahoward .. Thank you , i have already raised this in the ideas portal.  Regarding the backward traceability yes the coverage report shows you the linkage of defect to testcases , but it does not show the traceability of the defect all the way back to the userstory/epic.

  • deitahoward's avatar
    SmartBear Alumni (Retired)

    Ah right, I see what you mean. 

    Can you explain what you're trying to use this information for? I'll have a think if there are any other approaches. 

    • kennedy's avatar
      New Member

      In our case,  when we deliver our Epic to cross functional teams, we would like to present details

      Epic1 -> Story1 -> Testcase1 -> Test Exec1
      Epic1 -> Story1 -> Testcase2 -> Test Exec1

      Epic1 -> Story1 -> Testcase2 -> Test Exec2

      Epic1 -> Story2 -> Testcase1 -> Test Exec1


      Which was possible with on-prem