...
However, have you provided credentials in Confluence for Requirement Yogi, as explained in the Release 2.2?
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:
What if we don't like the new panel?
- Please notify us and explain us. We may find solutions to improve your situation, and more importantly, we want to know about it before we go further with this implementation.
- Disable the panel: Go to UPM (the plugin manager), in our plugin, in the list of modules, disable the modules "issue-view-panel" and "sprint-board-panel" in UPM.
- Set up the custom field instead (see below). The custom field will take a much smaller visual footprint.
...
Checking the upgrade job
The data should migrate automatically from RILs to our panel:
...
- The job executes tasks which are in AO_42D05A_AOTASK.
- The job stops when there's a task with type="UPGRADE_RIL_SUMMARY" and value="FAILED" or "SUCCESS".
- The job uses OfBiz to query data. If it can't, for any reason, the you can create items yourself in the table:
- For each issue to migrate, create 1 AO_42D05A_AOTASK, with type='UPGRADE_RIL', status=null and details=the jira issue id or key ("10001" or "JRA-1" are both valid).
- Then go to the administration and click "Relaunch".
...
New features!
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:
What if we don't like the new panel?
- Please notify us and explain us. We may find solutions to improve your situation, and more importantly, we want to know about it before we go further with this implementation.
- Disable the panel: Go to UPM (the plugin manager), in our plugin, in the list of modules, disable the modules "issue-view-panel" and "sprint-board-panel" in UPM.
- Set up the custom field instead (see below). The custom field will take a much smaller visual footprint.
New custom field (optional)
The custom field requires the Confluence plugin to be upgraded (both should be 2.2.5+). You can add our custom field to your issue's screens to easily create links.
...
Note that for custom fields the plugin will fail to get the requirements description if you are running an old version of RequirementYogi (Confluence), so make sure to upgrade RequirementYogi to the latest version.
New JQL
...
function
We have now a JQL Function named requirementYogiLinks to search for issues that are linked to RY requirements.
...