Map records between Aha! and Jira Core

Most of the Jira integration capabilities are similar if you use Jira Software or Jira Core. The main difference is the issue types and how you map Aha! features and requirements.

Click any of the following links to skip ahead:

Tasks and sub-tasks

This is the recommended configuration if using default issue types in Jira Core.

Aha!   Jira
Feature > Task
Requirement > Sub-task

Note: Requirements will be created as sub-tasks of task issue type linked to the parent feature.

Top

Tasks

If using integrations 2.0 for Jira, you have the option to map tasks to epics. This is most appropriate when sub-tasks in Jira are larger, more descriptive work items, and tasks themselves take multiple releases to be complete.

Aha!   Jira
Epic > Task
Feature > Sub-task

Note: Features will be created as sub-tasks of task issue type linked to the parent epic.

For help configuring the rest of the Jira integration, please refer to the Integrating with Jira document articles for integrations 1.0 and integrations 2.0.

Top


Was this article helpful?
1 out of 4 found this helpful