We have a large set of requirements documented in a BRD on our confluence page. From here we are creating user stories and would like a way to link the specific requirement from the large page of requirements within the JIRA story. Preferably in the Requirements ID field.
How can I create a unique ID to associate with the requirements that can then be referenced in this way?
Linking to the entire page isn't useful or traceable at the unique requirement level.
Any help would be appreciated. We are not in a position to purchase anything from the Atlassian Marketplace so it would have to be a solution using JIRA and Confluence out of the box.
Thanks all
Hi again @Amie Fudge, I thought of something else:
You could use Confluence's "Table of Confluence" macro to get a reference link to each section of the page. In the example below, the link to the "Requirement 1" header is unique. It's in the format:
YOUR-JIRA-URL/wiki/spaces/~rwright/pages/123456789/Test+for+Amie#TestforAmie-Requirement1
But, this breaks easily if anyone changes the header copy (ex: "Requirement 1") on the page. I still think the "one requirement per page" idea is much better.
Rachel Wright
Author, Jira Strategy Admin Workbook
Thanks @Rachel Wright I'll try this - we have over 200 requirements so one per page would be a nightmare
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is there a way to do the opposite? supposed you have a page for each requirement how do you link it to an issue?
What I am asking is , when i am creating an issue in jira is there a way to have a field or link to a confluence requirement from within jira? so i can search and see how may issues are linked to this requirement?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @[deleted], it's easy to do this if your Jira and Confluence applications are connected via an "Application Link."
Here's an example of linking a Jira issue to it's related Confluence page.
In the Jira issue
Click More > Link and change the link type from "Jira Issue" to "Confluence Page." You'll find this option in the left sidebar of the linking overlay. The result adds the page in the "Issue Links' area with the other linked Jira issues.
On the Confluence page
Simply paste a Jira issue's URL into any Confluence page! It will create a dynamic link to the issue and pull in the icon, key, summary, and status. You and also insert a Jira issue macro for single or multiple issues.
For your search question
Any Jira issues linking to the specific Confluence requirement page are totaled and listed at the top of the page.
Hope this helps!
Rachel Wright
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
that's brilliant , thank you Rachel!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Amie Fudge, the only way I can see to do it is to create a separate Confluence page for each requirement. Confluence and Jira already give you the needed unique IDs, the problem is you only have one Confluence page ID right now, since your requirements are all stored on the same long page.
And, as you probably know, if your Jira and Confluence apps are linked together, you can simply reference the Jira issue ID on the Confluence page to dynamically link them together.
Hope this helps or at least creates more conversation,
Rachel Wright
Author, Jira Strategy Admin Workbook
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Rachel Wright. Sounds like there isn't a confluence macro that I can use to insert an id for elements on a confluence page. Do you know if that is in the works? It would be very useful
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.