Ability to choose how each Aha Initiative/Feature/Requirement should be mapped to JIRA, as opposed to one mapping setting for an Aha product.

As a user, when creating a new Aha Initiative or Feature, I would like the ability to choose whether the Aha Initiative/Feature/Requirement should be mapped as a JIRA Epic, User Story, or Requirement, so that I can have more flexibility when creating new Aha Initiatives/Features/Requirements (instead of being locked into a single Aha-to-JIRA integration mapping scheme).

ADMIN RESPONSE

Jan 26, 2016

As noted, currently the Aha!/JIRA integration is configured in a way so that there is a consistent framework in terms of how objects are related to one another. There is flexibility in terms of which objects can be linked across the two tools. This is done in a way which allows both environments to be created in a way which can easily scale.

Please note that integrations can be set up for each product, so there is flexibility in terms of how the integration works across different products.

However, we are unlikely to make changes in this area to allow for individual initiatives/features/requirements in Aha! to be linked to any object in JIRA as this would potentially create a framework with limitations. We hope you can understand.