The release retrospective report provides many useful data points. I would like to pull this information into reports so I can, e.g., view more information about records that were removed from a release.

What is the challenge? The bubble chart has a fixed sort that's based on the "Labels" dropdown field in the chart configuration What is the impact? The built-in sort by the "Labels" does not allow for sorting the axis separate from the lab...

What is the challenge? Currently, Feature Goals show as a tag when included in a Feature Prioritization list report. Unlike Initiatives that appear as a link. This means that Feature Goals cannot be expanded and opened in a details drawer to vie...

In our department we have developer teams working with Jira but also other teams for e.g. process improvements, consultancy... It makes no sense to track their work in Jira as they only need a simple board for their needs. Currently they use the M...

What is the challenge? Today Aha only allows to send the Release field from Aha to Jira, while we have technical teams that use only Jira (developers) and update the release there, while it can't sync back to Aha. What is the impact? Incon...

What is the challenge? Cannot incorporate custom tables in any of the prioritization views. What is the impact? This would allow for teams to include relevant information from custom tables when utilizing the prioritization view. Our te...

What is the challenge? Today if a team has multiple email aliases for their users there is no easy way to stop the creation of duplicate accounts across Roadmaps and Idea portals. What is the impact? A single person may have an Aha! accoun...

What is the challenge? We have users that work for several different orgs because they offer technology or professional services. They have a separate email for each organization that they support because they are licensed users in their respect...

Currently with a Pivot chart you can choose to include a Total row AND column. For many pivot charts, only one of these makes sense and the other is useless space wasting data.

We need the ability to make standard and custom fields mandatory for existing records. When a record is being edited, the UI should flag empty required fields so that the user is prompted to update them. This will help us ensure that critical inf...