More flexibility in Mapping Initiatives with JIRA Merged

I;d like the option for Aha Initiatives to appear in JIRA as fields in an JIRA issue.

Our company does not use JIRA sub-tasks for Feature requirements. We use sub-tasks for tasks needed to deliver the requirements--engineering tasks, QA tasks, etc. Therefore we need to map Aha features to JIRA epics and Aha requirements to JIRA stories. This means we cannot map Aha Initiatives to JIRA epics as currently delivered.

Similar to the way Aha Initiatives appear in Aha Features, I'd like the option for the Aha initiative within a features to appear as a field in the JIRA Epic. As shown in the image