| Excerpt | ||||
|---|---|---|---|---|
|
- Search and link to requirements from JIRA,
- Confluence displays the link in the Requirement Yogi inline dialog,
- The text is updated in JIRA whenever users click "synchronize" for an issue.
Example:
Inserting a requirement:
Information page in Confluence
If you move a requirement to another space in Confluence, the link from JIRA is not updated. Don't worry, users will be redirected to the new space as long as no requirement is created with the same name in both spaces.
It is therefore useful to synchronize requirements between Confluence and JIRA. A synchronization can either be triggered from a JIRA issue (see screenshot above) or from Confluence. We've included this feature in the Tools menu, on the top-right of the page:
Installation
To install this module, please:
- Check both JIRA and Confluence have the same version of Requirement Yogi,
- Create an Application Link using OAuth between JIRA and Confluence (see Atlassian's documentation),
- Create an Entity Link between the JIRA project and the Confluence space (see Atlassian's documentation).
When search for a requirement from JIRA, Requirement Yogi will only search Confluence instances which are linked with the current JIRA project.
| |
You can have an efficient requirements management in Jira, thanks to our integration plug-in. Learn how to use it now. |
To use all Jira connected features, make sure you download the Requirement Yogi for Jira app first.
How to set up the integration?
Set up the 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 Go to the Requirement Yogi for Jira configuration page for more explanations
What does the integration look like in Jira?
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: |  |
What does the integration look like in Confluence?
The glorious Jira bulk issue creation: |  |
And of course, Jira issues appear in the popup as dependencies, and in the traceability matrix. |  |
More about 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
JQL function
The JQL function to search for issues with Requirement Yogi links is described on this page: JQL Syntax.
Related content
| Child pages (Children Display) | ||
|---|---|---|
|