...
- 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 new panel,
- A JQL function, so now you can search for all issue linked to a requirement.
...
- Check that you can see/add/remove Requirement Yogi links properly in a Jira issue,
- Check the progress of the upgrade job (see below).
...
Notes:
- Have you provided credentials in Confluence for Requirement Yogi, as explained in the Release 2.2?
- If you have anything that relies on RY's "remote issue links", you will have to migrate it. For example, if you have a workflow validation checking for the presence of a "remote issue link", you will have to replace it. For example, you can set up the Requirement Yogi custom field for this project, and make this field mandatory at that step. If you have a JQL function that relied on "remote issue links", you will have to use our JQL function instead, etc.
Checking the upgrade job
The data should migrate automatically from RILs to our panel:
...