Traceability table between different issue types

How could I create a traceability matrix between requirements-test cases-bugs using Zephyr?

3 answers

Hi Fabiola

You can in part setup a traceability matrix with Zephyr for JIRA. Let me explain.

Use the "Linking" functionality of JIRA issues. Thus you can have a requirement that is "Covered By" a testcase and a testcase that is "Related To" a defect.

Zephyr 1.7 automatically creates the link to a defect when a defect is filed from testcase execution.

Reporting on this isn't as easy on the UI side. For example you'd have to do a lot of clicking to navigate through all the links.

There is however the potential to use the JIRA APIs to create a matrix reports based on your requirements, links to any testcases and any related defects. If you need assistance with creating an API report, please contact JIRA support.

We do offer a JIRA Gadget that assists in this realm. The Gadget is called "Top Defects Impacting Testing" and displays the defects that affects the most testcases within a specific JIRA Project and Version Combination.

Kind Regards,


We have just released a traceability matrix plugin. You could download it from this link:


  • Bi-directional traceability matrices and issue link graphs can be generated by this plugin.
  • One can report traceability between different issue types such as features, stories, tasks, tests, bugs and other custom issue types.
  • Change impact analysis can be done more objectively since this plugin provides which issues are directly or indirectly linked to the issue that is being changed.
  • This plug-in helps organizations to satisfy requirements management process area SP 1.4 Maintain bidirectional traceability among requirements and work products”
  • Fields which will be displayed on the traceability matrix are selected by the user.
  • Bi-directional traceability reports are generated in Excel or HTML format.
  • Bi-directional traceability reports can be filter or project based.
  • Issue relation graph tab shows all other issues which can be affected by a change on an individual issue. The issues can be either directly or indirectly linked to the individual issue.
  • Issue details are shown on the graph.

Hi Fabiola,

If you express the relation between your requirements, test cases and bugs using issue links, then the PDF View Plugin delivers an immediate solution. It has a traceability matrix template which is renders (bi-)directional arrows between issues if a link of certain types is present between the two. The set of input issues is defined by saved filter or any arbitrary JQL query, so the possibilities for filtering are limitless.

If you express the relation in a different way, like "issue reference" or similar type custom fields, then the logic used by this plugin can be easily modified as that is defined in an editable Groovy script.

See the screenshot or this actual sample Traceability Matrix PDF

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 07, 2019 in Marketplace Apps

A Timeless Love Story

It started as any story starts, on a normal, rainy day.   Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...

452 views 8 26
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you