...
- A custom field for requirements, optional. It is particularly useful in the following situations:
- If you want to link to requirements in the Create Issue form, which you couldn't do before,
- If you want to require a link to a requirement at any step, including the Create step,
- If you want to preset the relationship so the user can't change it.
- A JQL function, so now you can search for all issue linked to a requirement.
Do administrators have anything to do?
No, in theory. You can:
- Check that you can see/add/remove Requirement Yogi links properly in a Jira issue,
- Check the progress of the upgrade job (see below).
New panel
Since we don't store them in "Remote issue links", they don't appear as part of the normal panel. They now appear in a new panel, which only displays if there are requirements attached to the current issue:
...
Usage: issue in requirementYogiLinks('applink_id', 'relationship', 'space_key', 'key#baseline_number')
Examples :
| Example | Intent |
|---|---|
| requirementYogiLinks('REQ-001') | Issues linked to requirement REQ-001 |
| requirementYogiLinks('REQ-001#3') | Issues linked to requirement REQ-001 in baseline 3 |
| requirementYogiLinks('resolves', 'REQ-001') | Issues linked with relationship "resolves" |
| requirementYogiLinks('abcd-fff1-acef-4343', 'resolves', '*') | Issues linked to requirements from applink 'abcd-...' with relationship "resolves" |
| requirementYogiLinks('abcd-fff1-acef-4343', '*', '*') | Issues linked to requirements from applink 'abcd-...' |
| 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.
...