Ability to update Jira Affects Versions field from Aha via integration

What is the challenge?

Our Jira project has the Affects Versions Jira field configured as a required field. The integration only allows for a uni-directional update from Jira to Aha so I get an error when pushing Aha items to Jira. Because of this, I can't create new Jira issues from Aha and can't use the integration without removing the required field configuration in Jira.

What is the impact?

Unable to use the Jira/Aha integration without removing the required field configuration on the Affects Versions Jira field.

Describe your idea

Allow for the Affects Versions field to either be bi-directional or allow for a one-time update from Aha to Jira when items from Aha are initially created in Jira. Similar to the Created By User (Aha) to Reporter (Jira) mapping.