Import features from Jira (integrations 1.0)

This support article refers to the Aha! integration 1.0 version for Jira.

You can import issues directly into Aha! from Jira (you must be an Aha! Product Owner and have already set up the Jira integration). There are two good reasons to do this:

  1. To seed your account with features already captured in Jira.
  2. To incrementally add features to Aha! that have been created in Jira after your initial upload.

You can also link features in Aha! directly to an existing issue in Jira, this is separate from the Jira import functionality and is done through the Send dropdown next to the integrations field on a feature. Once you import — or link your feature — the connection between the issue and your feature will be active.

Which issues are imported?

The import allows you to enter JQL strings to filter what is imported. The default JQL string for the import is: status in (Open, "In Progress," Reopened).

That means that by default it will import every issue matching those statuses. If you want to import only specific issue types or any type of other custom filters, please refer to the end of this article on the easy to way create your own JQL strings.

The handling of Jira Issues that are not included as part of the integration mapping will be dependent upon the integration configuration setting Only auto import mapped issue types. If the checkbox is selected, only issue types that are defined in the integration mapping and match the JQL statuses will be imported into Aha! as features and requirements. If this checkbox is not selected, issue types that match the JQL statuses but are not included as part of the integration mapping will be imported as features. 

Which fields are imported?

Any of the integration fields available in the Jira integration to Aha! are supported in the import process. This includes epic, feature name (user story), requirements (sub-tasks), description, attachments, custom fields (features and requirements), assignee, and estimates (story point or time). 

Avoid duplicate epics

If epics are mapped to Aha! initiatives, you should import the epics from Jira to Aha! before you start creating initiatives in Aha! This will avoid the creation of duplicate epics. If you do send the epics to Jira and get duplicates, you should move the existing Jira stories to the new Aha!-created epic, rather than the other way around. This will correctly maintain the story links in Aha!

Import estimates

When importing backlog items to Aha! from Jira, you can also import estimates. Make sure that Aha! and Jira are using the same unit of measure for estimates (time or story points). Review our "Plan capacity by estimating effort" article for help setting up capacity planning. 

  • If you are using time for your units of measure in the release, then the original estimate and remaining estimate are imported from Jira.
  • If you are using story points for the release you import into, then the current story points value will be imported into both the original estimate and the remaining estimate.
  • The feature logged effort will be updated to reflect work that has already been logged for that issue in Jira prior to the import.

IMPORTANT: You cannot import from Jira until you've configured the Jira integration

Import features from development tool

Ensure that you are on the correct Aha! product by checking your navigation menu. Go to
Settings ⚙️> Workspace > Import from development tool. If you don't see this option, you either are on a product line instead of a product or you don't have the proper rights. 


  1. Choose the Jira 1.0 integration that you want to use and click Save and continue. Click Continue in the pop-up message to redirect to the Jira 1.0 import.
  2. Choose the Aha! release (or parking lot) where your Jira issues will be imported. Only issues that have not already been imported will be uploaded into Aha!
  3. Choose the Jira project that you wish to import from.
  4. We suggest that you use the default filter to import all open, "in progress," or re-opened issues. You can also specify a JQL string that can be used to further filter the issues that will be imported.
  5. Test the import. If the test is successful, we will return a message that shows the number of matching issues. This number will include issues that have already been imported into Aha!
    • Note: If you are not sure if issues have been uploaded before, it is safe to import again — no duplicates will be created.
  6. Complete the import from Jira. Once you import, go to your features board to confirm that all of the issues were imported as Aha! features and requirements. 

The import will take place in the background. It may take several minutes or longer depending on how much information must be imported.

Contact us at with any questions. 


Creating a JQL string
The following explains how to quickly and easily create a JQL query to filter information that is imported into Aha!

1. Use the Search for issues feature in Jira to add filters that will select just the issues that you want to import. For example, you could search by project, by status, or both. If the syntax is wrong when you type in your search, Smart querying should be activated. It will cause the JQL string to appear in your search bar and prompt you for what you want to search. 

2. Click the Basic link next to your search results if you don't already see the Advanced link. 


2. Click the Advanced link to the right of the search bar to see the JQL expression that corresponds to these filters:
3. Copy and paste the JQL into the Aha! import window.

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