Do not allow requirements to be mapped without a Links To relationship set

It is possible to create an integration where you have requirements mapped to a Jira record type, and where you have no Links To relationship established to a parent record in Aha!

This results in import errors where requirements cannot be imported into Aha! because they cannot be linked to a feature and cannot be orphans.

Suggestion:

• Do not allow Requirements to be mapped without a Links To relationship set

• OR

• When adding the requirement record mapping into an integration, default the links to relationship to the parent like we do on new integrations