Manaully Link Requirement to Feature from Integration Updates Merged

We have an integration from Aha to a JIRA "next gen" project. As a result, we have lost the ability to set up a "Link-to" option. So when a Requirement is created in JIRA (for Features that are linked between Aha and JIRA), the new Requirement is NOT automatically sent to Aha under the correct Feature. Instead it ends up in the "Integration updates" bucket. We can't use the "Import Selected" option - this end up with an error.

We also can't reliably create a new Requirement in Aha and try to link it to the Requirement in JIRA - if we are too slow, Aha will automatically create a NEW Requirement in JIRA, so we end up with a duplicate! With this mess, we have to now delete the link to the NEW JIRA requirement, re-link to the original one, and delete the NEW Requirement in JIRA. A big pain!

I want to be able to take a Requirement from the "Integration Updates" bucket and manually link it to the correct Feature in Aha!. I assume this would work in a similar way as when you move a Requirement from one Aha! Feature to another.

Not being able to import a Requirement that is a child of two linked Features (because the JIRA project is a "next gen" project). It seems like this would be a useful feature regardless of the DEV system that Aha is integrated.