You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In my past program, we developed requirements in JIRA and test cases in JIRA but assigned the test cases a separate issue type.
By using Confluence, I would drag the requirement ticket into a table in Confluence.
Then any test cases, attachments, text or clarifying comments were entered into the Confluence page (either in the table cell or in the page's comments section)
Defects were also mapped against requirements so the team could understand which requirements still had open defects.
I use this approach now when brainstorming requirements for a project.
At the start of the project, the requirements are very high level. By using Confluence and JIRA, I refine the requirements into separate tickets, drag them into a Confluence page and then have a nice requirements traceability matrix with ongoing documentation.
Hi - Here is a screen shot of a simple Requirements Traceability Matrix in Confluence using tasks/users stories or any JIRA issue type.
Just create table, manually enter the high level requirements and drag the detailed user stories into the table.
I find it very useful to break down high level requirements into user stories and track the delivery of the high level requirement to the detailed user story.
When you are first defining scope, it helps to identify the high level requirements and then map to the detailed requirements.
Let me know if you have any questions!
Hi - good info thanks. I am relatively new to JIRA. The part I am having trouble with is as follows, if you can help that would be great.
For example: Auditor needs to track a financial approval process. I need to be able to confidently go back to the business and demonstrate how the story was delivered.
The Dev Team may close, reword, split / merge with another story - this is where it gets hard to track the original story.
I am looking for a dynamic update.
It looks like I need to build this table up so I'll also look to add Epics, Sprints and Acceptance testing
Below is my Question link
Also fairly new to Jira and Confluence.
Are you able to expand on your comment
'By using Confluence, I would drag the requirement ticket into a table in Confluence.'
From what view in Jira are you able to drag a ticket?
I do not know of a way to drag a ticket; I assume that it relates to copying the link to the issue (copy from the URL line in your browser) and past it in the specific location in the Confluence table where you want it to appear.
The Jira issue will be displayed nicely in Confluence and link to Jira.
For all test app lovers, requirements and issue mangers looking for an app to organize and trace your links from e.g requirements over implementation tasks to test case:
Additional to a flexible, free structure to organize any kind of issue in your hierarchical tree we
If you interested, give it a try/trial or ask for a free tool demo.
BTW, test cases can be from any test app, also from our T4J - Test Management for Jira, as long they are Jira issues.
Have a great day, Bernhard
Sorry for the late response. I miss the notification.
TraceabilityX app is not Cloud Compatible yet.
We are working to make it possible, but it is too soon yet to share a roadmap.
Stay tuned and do not hesitate in reaching us if you have any comments or questions.
an App which is available for Cloud is: Jira Snapshots for Confluence . Assuming you use Jira links (or other ways of Jira relations) between your traceability items, then this will allow you to create static traceability views in Confluence.
PS: If you don't have Confluence you can just spin a free Confluence and use it there.
PS2: the listing has a short video that takes you through a demo.
(Disclosure- I am from the developers of this App)
Hope this helps,
I am not sure you are still part of the development team for "Jira Snapshot for Confluence". It is a great tool to create a tracibility report from Jira.
But the sorting (such as by Sprint or Label) of second level or third level is not working properly as intended.