Automatically push Epics/Features in Aha! to JIRA

What is the challenge?

As a product manager using Aha!, I want to be able to create an Epic or Feature and have it automatically push to JIRA (even it's a shell that is not definition complete), so that it is represented on the JIRA board where I do most of my work for further elaboration.

What is the impact?

Product managers today often create Epics/Features in Aha!, but then forget that they need to "push" them to JIRA via the integration button click. As a result, they never make their way to JIRA, and get lost. Or, even worse, the product manager ends up creating a duplicate epic in JIRA, forgetting that they already started one in Aha!. Since product managers at my company do most of their work as product owners within JIRA, and JIRA is our primary system for product development, this makes it harder to reinforce the Aha! and leads to unnecessary and duplicate work for folks to get their epics in alignment across Aha! and JIRA.

Describe your idea

The solution to this problem would be allowing the Aha! admin to set up an automatic epic/feature push to JIRA that is configurable by record type and workspace. Some companies may have the need for this and some may not, so providing the option would be great.