Aha! record mappings for Jira Core (integrations 1.0 and 2.0)

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.

Tasks and sub-tasks
This is the recommended configuration if using default issue types in Jira Core.

Aha! Jira
Feature -> Task
Requirement -> Sub-task


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

Tasks 
If using integrations 2.0 for Jira, you have the option to map tasks to Master features. 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
Master feature -> Task
Feature -> Sub-task

Features will be created as sub-tasks of task issue type linked to the parent Master feature.

 

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.

Was this article helpful?
1 out of 3 found this helpful
Have more questions? Submit a request

Roadmap software to manage your products.
Finally, connect strategy to execution.

Powered by Zendesk