...
If you are having questions on what to / parent, from / children mean, read this page: https://confluence.intranet.requirementyogi.com/wiki/spaces/RYC/pages/2564128774/Requirement+dependencies#I-cannot-remember-what-TO-and-FROM-is-%3F-What-is-the-direction-of-dependencies%3F
...
Upgrade from Connect API to Forge
Atlassian will migrate the API of Marketplace apps from the framework Connect to Forge (Announcement here). Before version 2.2.0 our apps were based on Connect, we have now migrated to Forge.
What you need to do (as an admin): Click on the update button in the Atlassian administration > Manage Apps.
Forge app permissions have different mappings than Connect’s, so we requested Atlassian to approve our current app permissions to map with Forge’s. The app permissions remain the same as before, we are not requesting more permissions than before, simply converting the old ones into the new system. (You can find that information in the Marketplace Apps Administration > Requirement Yogi > Authorisations)
What you need to do (as a user): Nothing.
What changes for you now: Nothing.
What will change for you in the future: Migrating to Forge opens us to new Atlassian features to integrate with, which will allow us to develop new features through different ways. (We may be able to implement the famous DC Requirement Popup into the Cloud, and more
. So stay tuned for more awesome features).
Minor Improvements
UI/UX :
External Properties: Improvements in the Requirement Detail.
Variants: Minor improvements on management page
Traceability: Improvements on total values displayed with external properties number.
Queue (for Admins): Improvement on pagination
Cleanup tasks: Improvements
RY for Jira panel: Improvements - removed search when they are no requirement links)
Technical:
Improved accuracy of API error messages