Aha! Roadmaps | Send changes and accept imports from another system

Integrating Aha! Roadmaps with a development system allows your team to do all of their planning in Aha! Roadmaps and then send planned work to your preferred development system. For each integration that you set up, you have several configuration options for sending updates and importing records.

Click any of the following links to skip ahead:

• Manually send records from Aha! Roadmaps

• Update integrated records

• Accept imports from your development system

Manually send records from Aha! Roadmaps

The following integrations are available for integrations 2.0:

• Azure DevOps Services

• Azure DevOps Server

• GitHub

• GitHub Enterprise

• Jira

• Rally

• Trello

To send a new record from Aha! Roadmaps to your integrated system:

1. Open a feature or activity card and navigate to the Integrations section, on the Overview tab.

2. Select an integration from the dropdown list of integrations to Send to.

After you have sent the record from the Aha! Roadmaps side, the record is linked and updates will flow back and forth between Aha! Roadmaps and your development system.

If a record that you are working with already exists in your development system, you can also link to an existing record in your development system.

Top

Update integrated records

Two options are available in Settings ⚙️ Workspace Integrations for handling outgoing changes:

• Approve outgoing changes: If you select this option, a workspace owner or contributor will need to review and send every change.

• Automatically send outgoing changes: This is the default option. Changes in Aha! Roadmaps will be sent immediately to your development system and no additional action is needed.

If you choose to approve outgoing changes, navigate to Settings ⚙️ Integration updates, then use Send outgoing changes tab to review changes.

When you open the Integration updates modal, you will see a filtered list of pending outgoing or incoming updates.

To send an outgoing change:

1. Click any record to view the details of the change.

2. Select a checkbox for each change you wish to send to your integrated development system.

3. Click Send changes to approve and send the change(s).

There is a five-minute delay when sending description field updates. This delay allows Aha! Roadmaps to batch the updates and make one update instead of many.

Top

Accept imports from your development system

Two options are available in Settings ⚙️ Workspace Integrations for handling record imports:

• Approve new records before importing: Records will not be imported until they are approved. If you add a record to your development system that is mapped to an Aha! Roadmaps record type, the record will display in the Integration updates modal as an import option. The Integration updates modal allows you to review new record details prior to import. When you are handling incoming records that are mapped to multiple integrations, you can select the integration to use when importing the new record.

• Automatically import new records: This is the default option. If this setting is enabled, new records will be automatically imported only if they are children of a previously linked parent record. This applies to records that are linked to initiatives, releases, schedules, epics, features, and activities. If the imported records are not children of a previously linked parent record, a few different things can happen. We will use features as an example:

  • First, the status quo: if a feature's parent release is linked with Aha! Roadmaps then in Aha! Roadmaps the feature will be contained within that release.

  • If a feature's parent release is not linked with Aha! Roadmaps, if the feature does not have a parent release, or if releases are not mapped with the development system at all, then the feature will not be automatically imported and will instead display in the Integration updates modal as an import option. After the import is approved by a workspace owner or contributor, the feature will be imported into the first parking lot release. This is by design, since the parking lots are repositories for unscheduled work.

    When you use this setting, if an Aha! Roadmaps user does not take action on an import record (using either the import or ignore action), and that record later gets added to a parent record in the development system which is already linked to a record in Aha!, the child record will be automatically imported.

When the import occurs, Aha! Roadmaps always imports the most up-to-date copy of the record — so there is no need to worry about missing changes that might occur while you are reviewing.

Top