Aha! Roadmaps | Import data from your development system

Excited about Aha! Roadmaps — but all your data is in your development tool? Do not worry!

You can import records directly into Aha! Roadmaps from your development tool of choice (and even create an integration with that tool at the same time). Once imported, your records will retain their link to the development system, so that you and your development team can collaborate on the same records at once.

Only workspace owners can import data to a workspace.

Click any of the following links to skip ahead:

• Import records

• Items to note

Or see more information on the integrations that support development tool imports:

• Asana

• Jira 1.0 integrations

• Jira 2.0 integrations

• Rally 2.0 integrations

• Azure DevOps Services and Azure DevOps Server 2.0 integrations

• GitHub and GitHub Enterprise 2.0 integrations

• Trello 2.0 integrations

Import records

Navigate to Settings ⚙️ Workspace Import from development tool.

1. First, choose whether you want to import from an Existing integration, or create a New integration and import records from there. Note: If you choose a Jira integration that is running integrations 1.0 you will be prompted with a message and taken into the original 1.0 Jira import workflow.

2. Next, select the integration you want to use for your import.

3. Select which types of records you want to import. The type of records you can import depends on the integration you select, but generally you will be importing records from your development tool as Aha! Roadmaps features/activities, requirements, and releases/schedules. After selecting the record types you wish to import, you can add filters to the record type being imported.

4. Finally, you will see a list of the records you are about to import. Click Import records to import them.

Top

Items to note

1. Records you import will populate your Aha! Roadmaps workspace automatically.

2. Depending on your integration configuration, it can be difficult to import active releases and schedules without also importing all releases (or schedules). To avoid importing unwanted data, import features and activities instead of releases and schedules. The releases and schedules associated with the features and activities you import will be imported as well.

3. If you do import the wrong records by mistake, don't worry! You can bulk delete any unwanted records using a list report.

4. As records are imported into Aha! Roadmaps, Aha! Roadmaps may make changes to records in your development system:

   • For any fields configured to send one-way from Aha! Roadmaps, the import will update the field in the development system to match Aha! Roadmaps and create consistency. For example, this is useful when a hyperlink to the Aha! Roadmaps record is stored in a custom field in the development system — the hyperlink will be populated during import.

   • For the Github integration, a link to the Aha! Roadmaps record will be added to the end of the body of each issue.

5. In addition to importing from your development tool you can also import data into Aha! Roadmaps by CSV file.

Top