Ability to adjust the number of rows seen in a custom table per pagination. For some tables fewer rows and more pages is better for others more rows on fewer pages. Currently hard coded at 10 per page.

As a user, I would like the Master Features vs Features indicator to stand our more. So many times, I go to the features board get alarmed because I'm not seeing what I'm expecting to see. After I calm down, I realize that the view is flipped to m...

The options to calculate the completion of an epic in Aha is only based on user stories, but there are other items in JIRA that determine how complete an epic is. It would be helpful to have the progress bar completion automatically reflect whatev...

Hi Aha! Team, Having a filter that ommits certain options would help with reporting.

The cycle is great, but one key element is missing - it's the Product Design phase. I have to put it in "features" or "requirements", but design doesn't work like that. I'm unable to see/ demonstrate the work done by the design team, as there is n...

We look at the same Initiatives through two lenses: (1) the product lens, which Aha! solves really well; and (2) the program lens, which Aha! does not solve for. The idea is to have an Alternate Hierarchy in Aha!, such that the same initiative c...

For example, We may have our engineering team (or QA team) in Aha! as "reviewers" and we would like them to participate in escalating status - such as: Engineer would say "In Development" when they start, and "Development Complete" when done. Then...

It would be great if the Portfolio Roadmap can be customized. We want to display the roadmap on a television screen for the entire office to see, but we'd like to hide certain projects. Thanks!

We are looking to share a roadmap with external stakeholders from Aha. However, we want to control which external users can access in the case if an employee leaves on of our clients, we do not want them to retain access of our roadmap. Today, the...

Currently Aha stores user first and last names. In the get user and list users REST API response objects, those fields are combined into one field: name. So John and Doe just get returned as John Doe. This causes problems when you have many differ...