Aha! is web-based roadmap software. With Aha! you can set strategies, prioritize features, share visual plans as well as crowdsource feedbacks and engage a community. You can also use Aha! as a fully extendable agile development tool.

Data integration: Skyvia supports importing data to and from Aha!, exporting Aha! data to CSV files, replicating Aha! data to relational databases and synchronizing Aha! data with other cloud apps and relational databases.

Backup: Skyvia Backup does not support Aha!.

Query: Skyvia Query supports Aha!.

Establishing Connection

When creating a connection to Aha!, you have to to enter a subdomain and log in to Aha! via OAuth 2.0. The OAuth authentication token is stored on the Skyvia server. Your Aha! account credentials are not stored on Skyvia side.

Getting Credentials

To obtain the subdomain value for Aha! connection, you must do the following:

  1. Log in to Aha! and click the gear symbol on the top right corner of the page.
  2. Click Account and select Profile in the left menu.
  3. Copy the subdomain value from the Custom domain box.

    Connection Editor window

Creating Connection

To create an Aha! connection, perform the following steps:

Connection Editor window

  1. Paste your Aha! subdomain to the Subdomain field, which you can find in your Aha! account profile.
  2. Click Sign In with Aha!.
  3. Enter your email address and password used when registering in Aha! and click Log in.
  4. Give skyvia permission to access your Aha! account.

Additional Connection Parameters

Suppressing Extended Requests

For some objects, Aha! API returns only part of the fields when querying multiple records. In order to query values of additional fields, Skyvia performs additional extended requests. Such API requests can be performed for each record of such object. However, this can decrease performance and significantly increase the number of API calls used. The additional fields are the following:

Objects Fields
ProductPersonas Color
CreativeBriefs Color
Features Release_Id
Epics Release_Id

To reduce the number of API calls, you can select the Suppress Extended Requests checkbox.

Connector specifics

Object Peculiarities

  • Some objects like Goals, Initiatives, Epic, Releases, etc., contain the Watchers field. When querying data, data is not displayed in this field, but in import packages this field is available for mapping, and you can specify data that will be imported. The data must be specified as JSON array of Users Ids, fo example ["123456", "789456"], where 123456 and 789456 are Ids from the Users object.
  • The values for ScoreFacts field (in the Ideas objects) should be provided as a JSON array of objects, like the following [{"name": "Benefit", "value": 10}, {"name": "Effort", "value": 3}], where the name field contains the Score name, and the value field - Score value.
  • When querying data from the Features object, data in the Goals field is displayed as a JSON array of objects like the following:

               "body":"Description body for Goals - from Skyvia import",

    However, when loading data to the Features object, you need to specify Goal ids as an array of numbers (ids of the Goals tables) ([6984435874395374467] or [6984435874395374467",6984435874150517722]).

Incremental Replication and Synchronization

Replication with Incremental Updates is not supported for the following objects: AccountBackups, CapacityEstimateValues, CapacityScenarios,EpicCapacityInvestments, FeatureCapacityInvestments, IdeaOrganizations, InitiativeCapacityInvestments, ProductCapacityInvestments, ProductRoles,ProductTeams, ProductUsers, StrategyModels, StrategyPositions, Teams, Workflows.

Some objects, like Products, ProductPersonas, Notes, Releases, Competitors, Features, ToDos, ProductIntegrations and AccountIntegrations, return the value of their updated_at field only when querying separate records by their id. When querying all records, they do not return this field. This means that we cannot use this field when performing replication with incremental updates or synchronization. Replication with incremental updates and synchronization can detect and sync newly created records in these objects using their created_at field, but cannot detect changes made to existing records.

Skyvia supports Synchronization for such Aha! objects as EpicComments, FeatureComments, FeatureRequirements, GoalComments, Goals, IdeaComments, IdeaEndorsements, InitiativeComments, Initiatives, ProductIdeas, ProductPersonas, Products, ReleaseComments, ReleasePhaseComments, RequirementComments, ToDoComments.

DML Operations Support

Operation Object
INSERT, UPDATE, DELETE CapacityEstimateValues, Competitors, CreativeBriefs, EpicComments, Epics, FeatureComments, FeatureRequirements, Features, GoalComments, Goals, IdeaComments, IdeaEndorsements, IdeaOrganizations, InitiativeComments, Initiatives, Notes, ProductIdeas, ProductPersonas, ReleaseComments, ReleasePhaseComments, ReleasePhases, Releases, RequirementComments, ToDoComments, ToDos
INSERT, UPDATE EpicCapacityInvestments, FeatureCapacityInvestments, IdeaUsers, InitiativeCapacityInvestments, Products
INSERT, DELETE IdeaSubscriptions, ProductRoles
INSERT AccountIntegrations, IdeaPublicComments, ProductIntegrations, ProductUsers
DELETE EpicRecordLinks, FeatureRecordLinks, GoalRecordLinks, IdeaRecordLinks, InitiativeRecordLinks, NoteRecordLinks, ReleasePhaseRecordLinks, ReleaseRecordLinks

Supported Actions

Skyvia supports all the common actions for Aha!.