The use case is so that those working primarily in JIRA can understand “why” they are being asked to deliver “what” has been requested.
In the screenshot attached, it shows a section of the JIRA issue interface. It then shows a tab created specifically for AHA information. This is viewing the issue type Epic. You can see the Aha rank & the Aha reference.
Clicking on the Aha reference will take the user to the feature in Aha. This will contain the same information as the Epic already in JIRA. When viewed in that lens, the value of this link is therefore limited.
As a user primarily operating in JIRA, understanding what helps to articulate the how, but understanding the "why" enables confidence that the "how" is correctly meeting the acceptance criteria to deliver what needs to be done.
The request is is to ask for additional record links to be possible at master feature, feature and story level. If we can send across the link to the corresponding goal, and a separate record link to be able to send across the corresponding initiative, this will help with the Why. Further, if a third record link can be added which enables features to send across the link to any corresponding master feature, then the JIRA user will get all the information they need to understand why they are being ask what it is they need to deliver.