How to set up the integration
To enable the Confluence-Jira integration:
- Set up Application Links between Jira and Confluence,
- Set up Entity Links between a Jira project and a Confluence space (or several),
Go to the administration and set the credentials in both products (since 2.2 for Confluence and 2.5 for Jira).
Status colour Yellow title Important
|Set your credentials in Confluence||Set your credentials in Jira|
The user is used to send the queue messages between Jira and Confluence. When you modify requirements, we update their text in Jira; When you modify issue titles, we update the link title in Confluence.
What permissions are needed?
If I don't like providing credentials, how should I do?
This was introduced in version 2.2, so head to our release notes if you have more questions.
After adding your credentials, make sure you have "Entity links" between the Jira project and the Confluence space.
Overview of the integration
A Requirements panel on Jira issues:
A custom field, if you choose to configure it instead of the panel:
The dialog to add links on an issue:
The glorious Jira bulk issue creation:
And of course, Jira issues appear in the popup as dependencies, and in the traceability matrix.
The Custom Field
Using the custom field is optional. All requirements can be displayed in the "requirements" panel, but some customers prefer using the custom field, which makes it possible to:
- Make requirements visible in the REST API,
- Make requirements visible in the XML API,
- Make the field visible and mandatory on the Create Issue screen.
If interested, see more details on Release notes 2.2.5 for Jira
The JQL function to search for issues with Requirement Yogi links is described on this page: JQL Syntax.