Jira only (Data Center / Server)
This page relates to Jira only. The Jira module is free, Data Center-supported, and its installation is described in JIRA-Confluence integration for Requirement Yogi.
In 2.2.5, we've introduced a JQL Function named requirementYogiLinks to search for issues that are linked to RY requirements.
Usage: issue in requirementYogiLinks('applink_id', 'relationship', 'space_key', 'key#baseline_number')
Examples :
| Example | Intent |
|---|---|
| issue in requirementYogiLinks('REQ-001') | Issues linked to requirement REQ-001 |
| issue in requirementYogiLinks('REQ-001#3') | Issues linked to requirement REQ-001 in baseline 3 |
| issue in requirementYogiLinks('PROD', 'REQ-001') | Issues linked to requirement REQ-001 and spaceKey PROD |
| issue in requirementYogiLinks('abcd-fff1-acef-4343', 'resolves', '*', '*') | Issues linked to requirements from applink 'abcd-...' with relationship "resolves" |
| issue in requirementYogiLinks('abcd-fff1-acef-4343', '*', '*', '*') | Issues linked to requirements from applink 'abcd-...' |
| issue in requirementYogiLinks('resolves', '*', 'REQ-001#1') | Issues linked to requirement REQ-001 and baseline 1 with the relationship resolves |
Any argument can be replaced with '*' if it's not relevant.
The NOT keyword
The NOT keyword doesn't work well yet.
When deploying to customers, we've noticed many of them use JQL to detect issues which don't have requirements yet. This is not a usecase we've thought of, and it may perform badly. Watch
Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
to keep updated.