Traceability matrix of Jira issues against design documents in confluence

[Laurent Lemberger]

Hi

We are trying to produce a traceability matrix of Jira issues (epics) against design documents in Confluence (wiki) on our Jira Server instance.

Jira epics have been tagged on the relevant design document confluence pages for each design document.

We know that we can see the list of associated Jira issues at the top of every wiki page and can run a query against a specific page using Scriptrunner (we have this installed) and a JQL using the site ID & confluence page reference. We need to go further as we want to have a table that looks like this:

Epics          Design Doc 1           Design Doc 2            Design Doc 3

Epic 1                x                               x

Epic 2                x

Epic 3                                                x                                    x

Epic 4                                                x

This will help us to have traceability of Epic coverage against the design documents at a high level and any gaps. We have been looking into ways of doing this through Jira, Confluence, Power BI (using Rest API) and have not been able to be successful yet.

We have Scriptrunner, links hierarchy, eazyBI and x-ray plug-ins if any of those would be of use?

I have been searching this community forum and google but not found anything yet that fits our needs. I assume this would be a common query though.

Many thanks in advance

[Janis Plume _eazyBI_ · Accepted solution]

Hi,

The recommended solution with eazyBI would be to implement a scripted field in Jira collecting the confluence page list in a new field:

eazyBI allows importing such fields: https://docs.eazybi.com/eazybijira/data-import/data-from-jira-and-apps/jira-calculated-and-scripted-custom-fields#Jiracalculatedandscriptedcustomfields-EnablecalculatedcustomfieldineazyBIadvancedsettings

There can also be a close solution for importing the remote links using the Javascript calculated custom field in eazyBI, but there could be limitations in this solution.

Please, apply for eazyBI support for more detailed guidance.

Kindly,

Janis, eazyBI