How to Link Jira Issues in a Confluence Page (Requirements to Epics)
Connect your requirements in Confluence to the work in Jira: paste a Jira link and Confluence turns it into a live link with the key, the title and the status. Shown on a real requirements page.
Step by step
Why link them
- Jira in Confluence. Requirements live in Confluence and the work lives in Jira. When you link them, anyone reading a requirement can see whether the work is done.
- The requirements. This is a business requirements page. Each requirement belongs to an epic in Jira, and the epic is named in its own column.
Paste the link
- Edit. Click Edit to open the page in the editor.
- New line. Click at the start of the first line (Ctrl+Home takes you there) and type a label for the link: Jira epic:
- Paste the link. Next, paste the link to the Jira epic, https://princetheba.atlassian.net/browse/SCRUM-5. You copy it from the address bar while the epic is open in Jira. Then press Enter, so the rest of the page moves down a line.
- A live link. Confluence turns the address into a live link. It shows the key (SCRUM-5), the epic name and its status, and it keeps them up to date.
Share it
- Update. Click Update to publish the change, so everyone who opens the page sees the link.
- Click through. The published page now shows the live link. When the team moves the epic in Jira, the status on the page changes too. Click the link and you land on the SCRUM-5 epic in Jira.
- Status at a glance. Under Child work items you see every story in the epic, with its status and how much is done. The requirement and its work are one click apart.
Recap
- Paste the Jira link. To recap: copy the Jira link, paste it into the Confluence page, and Confluence shows a live link with the key, the name and the status.
Common mistakes
- Typing the key instead of pasting the link. If you type SCRUM-5 as text, it stays plain text, with no status and no link. Paste the full address from Jira so Confluence can turn it into a live link.
- Copying the address from the wrong Jira screen. Open the issue on its own page first, so the address ends in its key, like /browse/SCRUM-5. Then copy it from the address bar.
- Forgetting to click Update. Until you click Update, your change is only a draft and other people won't see the link. Publish the page after you paste.
- Readers who can't open the Jira project. The live link shows Jira details only to people who have access to that Jira project. Check that your stakeholders have access before you rely on the status shown on the page.
When a business analyst uses this
On a business requirements page you take to sign-off, paste each epic's Jira link into its row. Stakeholders can see each requirement's status right on the page, and one click takes them to the stories, so you don't have to send separate status updates.
Questions people ask
How do I link a Jira issue in a Confluence page?
Edit the page, paste the issue's address from Jira's address bar and click Update. Confluence shows it as a live link with the key, the title and the status.
Can I link a Jira ticket the same way as an epic?
Yes. Pasting the address of a story, task or bug works the same way as pasting an epic. Copy it from the address bar while the ticket is open in Jira.
