To avoid redundant third-party notifications, changes to the text editor are delayed by at least five minutes, waiting for five minutes after the most recent change.
Aha! Roadmaps | Integrate with Jira next-gen projects
Jira team-managed projects (formerly next-gen and classic) are designed to support smaller teams. Much of the project comes preconfigured for either a scrum or kanban template. When you integrate Aha! Roadmaps with a Jira team-managed project, Aha! Roadmaps will automatically detect the template type and create appropriate field mappings.
Click any of the following links to skip ahead:
Prerequisites
Integration type |
|
Supported versions |
Jira team-managed projects:
|
Aha! Roadmaps level |
|
Required user permissions: Configuration | |
Required user permissions: Use integration | |
Associated record types |
|
How it works
To integrate Aha! Roadmaps with your Jira team-managed project, follow the same integration process you would for classic Jira projects. This is a two-way integration, meaning information can be updated in either tool. Send your planned work to Jira, get notified when the Jira issue's status updates, and use comments to keep each team up to date.
Note:
Currently, you cannot map a single Aha! Roadmaps workspace to multiple Jira team-managed projects and move records between the Jira projects without losing record links.
Currently, if a Jira user story is assigned to a new epic or the epic is changed, Jira will not send Aha! Roadmaps a webhook, so Aha! Roadmaps will not know about the updated record relationship. The next time the record is updated (in Jira or Aha! Roadmaps), Aha! Roadmaps will be able to note and update the feature's epic.
Before configuring any integration for the first time, it is important to fully understand how to think about integrating Aha! Roadmaps with your development tool. Aha! Roadmaps should come first in the process — build out or import your records in Aha! Roadmaps, then send them to Jira. You can customize the ways that fields map to each other between the two tools, and even customize whether you want integrated records to update automatically, or only after your review.
This integration supports sending the following Aha! Roadmaps records to Jira:
Initiatives
Releases / Schedules
Epics
Features / Activities
Requirements
Versions are not enabled in team-managed projects by default, so while you can still map Aha! Roadmaps releases, you may choose not to.
Field mapping
Just like when integrating Aha! Roadmaps with classic Jira projects, you can customize field mappings between Aha! Roadmaps and Jira. Jira team-managed projects do have some different Links to... mappings, but Aha! Roadmaps will add those automatically for you (and you can change them if you need to).
As we mentioned in the introduction, Aha! Roadmaps will automatically detect your team-managed project's template and make appropriate field mappings. For example, stories and epics are both default issue types for scrum projects, but only epics are available in kanban projects.
If you get stuck, please reach out to our Customer Success team. Our team is made up entirely of product experts and responds fast.