We use automations to automatically assign ideas based on their categorization. Quite often ideas overlap product categories and as such multiple categories are assigned. The issue we are finding is that by adding the secondary categorization the ...

A very large icon has been added to the Aha feature cards to represent Jira integrations. Previously, the Jira reference number was shown as a hyperlink. The new icon has significantly increased the size of each feature card with no benefit and ha...

When the Feature Estimate field is initially set (t-shirt sizing / SWAG), and the 'Use tasks estimates' configuration is toggled to OFF, an 'Initial Estimate' value is displayed for the Feature. When child Requirements are added, with the Requirem...

We want to present the Ideas Portal as a link within our product. These are retail stores in our case often with a single email and login per store (shared across all retail staff). However the logging into the Ideas Portal requires the user to lo...

For timelines and other reports, we'd like to be able to segregate Master Releases from these reports. Now we end up with them appearing, which acts like duplicates, and usually need to perform some gymnastics to try to filter these out.

We have some custom fields that we want only to appear at the Product Line level, specifically for Master Releases and PL Initiatives. We'd like a way for them not to appear in Product Initiatives or Releases. As it stands now we just need to inst...

Show a clickable JIRA ID in an Idea once the Feature ticket has been sent to JIRA. Right now, Idea requester has to review reports to see if there is an associated JIRA ID. This would allow an Idea requester to easily go to their Idea and see if i...

We would like to see our work estimates by other fields not captured in the standard capacity report by creating a custom report. We are using the field "Week start" to show the estimates by month and those additional fields. However, we don't wan...

For a customer persona field, we would like to limit the Personas allowed to a defined level of product lines. So, the Product line immediately above the workspace, or 2 above. Or even by citing/naming the Product Line which would be the highest l...

Related to https://big.ideas.aha.io/ideas/APP-I-5692 In addition to adding fields lower in a layout hierarchy, it would be good to be able to remove ones that were not "essential". For instance, one of our teams (with a product line) do NOT want p...