October 21, 2016 release notes


  • We announced this week we acquired Roadmap.com and launched the world's first forum focused exclusively on product management. It is a site for education, connection, and even includes a special place for you to discuss everything Aha!. Register now at Roadmap.com.

  • Custom fields have been moved from the product level to the account level resulting in fundamental changes to their setup and configuration. The benefits behind this change including more control over where custom fields appear across your account are documented in this support article that was broadcast a week in advance of the update. This change means that an Admin - Customizations role in addition to a Product Owner role is now required in order to manage custom fields. It also means that you create a custom field once and all are viewable in one place: Settings - Account - Custom Fields. Adding a new custom field is a three step process:

    • Select the type of custom field you want and give it a name

  • Custom fields are added at the Account level in Settings - Account - Custom Fields.

  • Choose the data object you wish to add the custom field to -- Product, Personas, Competitors, Goals, Initiatives, Releases, Ideas, and Features.

  • Select the custom field type, give it a name and enter the rest of the required information.

    • Define how you want it presented on the screen through custom field layouts

  • Once a custom field is created, you need to add it to a custom field layout which determines where a custom field will appear on the screen.

  • Layouts based on your existing configuration were automatically created during the migration.

  • To add or modify a layout, go to Settings - Account - Custom field layouts. Within the layout page, you drag and drop the custom fields you want to be make visible on a screen into the section where you want it to appear, in your preferred order.

  • To remove a field simply move it back over to Available fields and it will no longer be visible in that layout.

    • Select the product(s) that will use the custom field by choosing its custom field layout.

  • Once you create a layout, they are assigned to the products you want them to be applied to. This is managed by Product Owners in Settings - Product - Configure.

  • Navigate to the Custom fields section and choose whether the product will use the layout inherited from its product line or apply a different one.

  • Custom tables (available to Enterprise+ customers) have also been moved from the product level to the account level. General setup and configuration of custom tables remains consistent with how it was done previously. The primary difference is how you enable an account level custom table for a given product. Go to Product - Custom tables and click on the new + button to use an account level custom table for that product.


  • Idea portal access can now be independent of IP address based access controls. This added flexibility is valuable for large enterprise companies that wish to have a public Ideas portal for their customers but otherwise lock down Aha! and Notebook access via IP address.

  • User permissions can now be managed through the Aha! REST API.

  • The Strategy - Goals and Strategy - Initiatives value & effort charts along with the Ideas - Chart views have been updated to prevent the text from being displayed outside of the chart boundaries. This is accomplished by displaying the icon on the left of the text in the left two quadrants and icons on the right of the text in the right two quadrants.


  • Any change in GitHub would result in the GitHub status overwriting the Aha! status even when the status in GitHub didn't change. This was a problem when using intermediate statuses in Aha!. This has been modified so that the Aha! status will only be updated when the GitHub status changes. The same logic also applies to the new label based status updates in the GitHub integration.

  • Users can click on a column header in the Reports - List view and perform an in-line edit to the name of their choosing. The revised column names were then displayed for those fields when viewing them in Report - Pivot views as pivot columns or pivot rows but not for pivot cells. Pivot cells will now also display the edited column value.

  • The display of Persona custom field tags as part of the Strategy - Overview - Competitors tab was displaying the values in double quotes in the competitor detail view. This has been fixed.

  • An edge condition was found where a Reviewer was able to edit an Initiative. This has been corrected.