Currently if you create a custom field of type Aha! record relationship - Products field then the values available for users of that field see the entire product hierarchy.We need to be able to filter that down to a specific Product Line and/or Pr...

Escalating this issue again here as it's now been moved to Atlassian's Long-Term Backlog & is critical to the adoption of Aha! at my company (as in people want us to go back to just JIRA bc syncing is so bad & data is out of date).  U...

Currently, when moving a Master Feature, there is the ability to move ALL related Features with it or move none of the related Features. Would be helpful to be able to granularly select which Features to move with a Master Feature.

We have some custom fields that are replicated for Epic, Feature and Requirement (e.g. Area Path for the integration with Azure DevOps). They have a long list of values we need to replicate and maintain three times instead of one. It would be perf...

Is it possible to configure an idea portal so when someone submits an idea that they can link their idea to multiple products? For example, in my company we have 35 brands which all have at minimum one product. We have a central digital advertisin...

When I go to Feature tab a new window "Create release" is always showed when I have no releases.

We have an idea review process for one of our Ideas portals that uses several custom fields. Two of these fields are used for the outcome (go/no-go and reason for decision). These fields can only be updated in the internal portal by users with pai...

For those who are using Azure to track application usage and performance it would be useful to have an integration that could display the feature usage metrics from Application Insights similarly to the Google Analytics integration.

It would benefit users who are trying to clean up a project that already exists. There may be information captured in pivotal that would be time-consuming to replicate.

The only way users can see the workspace Product ID is to pull a report. As a result, our workaround is to download the Product ID and upload it to a custom field on the workspace layout. This is a lot of manual work for something that is inherent...