What is the challenge? Currently, individuals that need to be part of more than one team can only have one schedule. Planned work in each respective team does not consume that individual's capacity and is not visible in totality This means tha...

What is the challenge? API keys inherit the full permissions of the user who creates them, and there does not appear to be a way to scope the key itself to specific workspaces, folders, or record types. This creates concern internally when bui...

What is the challenge? New version of presentations does not currently have field visibility controls for embedded record views. What is the impact? It's not possible to control field visibility, which leads to viewers seeing more informat...

What is the challenge? The prototypes created by Elle are extremely powerful accelerators - we are doing a workshop next week and plan to leverage this superpower throughout. The prototypes are visually pleasing but are very different from our...

What is the challenge? Currently there are fields in Aha that are Aha default fields. There is no way to adjust the terminology or tooltip for these fields to represent our usage of them. While creating a custom field is an option you lose some fu...

What is the challenge? - Within a workspace it's helpful to have consistency with the board views, including the card customizations. This avoids confusing stakeholders. What is the impact? - Currently, if the default card customizations are updat...

What is the challenge? It's not currently possible to report on a workspace's setting for Auto-shift dependent record dates What is the impact? You would have to go into each workspace individually to check this. Describe your idea Make this setti...

Request is to configure Aha! Roadmaps so that when a user is editing approval groups, they can differentiate between users that have identical or similar names by displaying the user’s e-mail address in parentheses, similar to the assigned to, wat...

What is the challenge? Migrating data (such as open ideas) into Aha! includes important historical context in comments. When creating internal idea comments through the API, all comments appear as made on the same created date which is confusing...

What is the challenge? When creating customer-specific “featuring” Knowledge Bases (KBs) from a source KB (e.g., selecting folders A and B), internal links inside articles keep pointing back to the source KB instead of the customer’s featuring K...