Note: This support article refers to the historical 1.0 version of the Aha! integration with Jira.
- If you are using the new 2.0 version of our Jira integration or would like to learn more about the new framework, see "Integrations — Development 2.0."
- If you are looking for details about custom field mapping for 2.0, see "Integration field mapping (integrations 2.0)."
Epics, stories, and sub-tasks
This is the most common configuration for Jira users, as it aligns closest to the Aha! data model. This mapping supports planning work at both the epic and the story level and accommodates for situations where teams have stories that exist by themselves without a relationship to a parent epic. This mapping also allows communicating epics that span across releases.
An initiative in Aha! represents a large strategic effort or project that the team is working on. Initiatives can span across releases and contain many features. From this perspective, an initiative is very similar to an agile epic.
You can link features to an initiative in two different ways:
- On the initiative detail view, there is a + icon that allows adding features directly to the initiative.
- On the detail view of a feature, there is an Initiative field that allows users to link the feature to any initiative they have access to within the Aha! account.
The initiative cannot be sent to Jira by itself. Initiatives only send to Jira as part of sending a feature to Jira. When you send a feature to Jira that is linked to an initiative, the initiative will be sent as an epic and the feature will be sent as a story linked to the epic.
Epics and stories
This mapping is the second-most common. It is popular when the product team in Aha! plans all of their work at the epic level. Since Aha! requirements are mapped to the Jira story issue type, teams using this mapping cannot create stories that exist independent of an epic. Requirements in Aha! can only exist as part of an Aha! feature.
For help configuring the rest of the Jira integration, refer to "Integrate with Jira cloud and on-premise."
For details around the advanced functionality of the Jira integration, see "Advanced Jira functionality."