We've tried to create a Traceability report for our release test plan and filter on fix version, but then it pulls hundreds of old stories and epics not a part of that fix version. Is there a piece we are not thinking of or forgetting here?
Hi @Nate Ryan
I am the product manager for a Marketplace App that can help. Sorry for recommending a paid app, but the native Xray traceability report is not always as nuanced as one needs.
A way to achieve this would be through Confluence, with the use of Jira Snapshots for Confluence and Snapshots Traceability Extensions for Jira Snapshots (the later is not required if you are on DC).
I recorded a short demo on youtube that explains how to achieve what you need.
Hopefully this can help,
Rina
Hi @Nate Ryan ,
There's a app for Confluence named Xray Reports for Confluence that can serve this purpose, if you're using Xray Test Management.
This app allows you to embed testing reports, based on data from Xray Test Management, directly into your pages in Confluence. It provides several macros tailored for this, that allow you, for example, to track traceability.
In your specific case, you can "use a saved filter" that picks only the Story and Epic issues assigned with the version you want, using the Fix Version field, and only those will be shown on the Traceability report. Then you can select the Test Coverage Scope to analyze them based on the tests and results reported against in some test plan. More info on the Traceability macro can be found in the docs.
To get it working, you'll need to follow these steps, which require installing not just this app on Confluence but also a "Connector" app in your Jira instance:
More info on the installation steps here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nate Ryan welcome to the community!
Could you elaborate more on 1) what plugins/tools you have used to create a traceability report? and 2) the steps you took?
Some other resources for your reference:
* Traceability report in JIRA (community discussion)
* Manage versions (docs)
Look forward to hearing from you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.