What is the challenge? Regular updates are needed for Aha Roadmaps shared on a company-internal site to ensure data freshness. Embedding only works when content is left unsecured, and linking to securely published content introduces some experienc...

In our development projects, features are often owned/assigned to more than one individual. Per intended use of the To Do's, we prefer to assignee the true list of owners to each feature versus creation of a To Do or use of the Program Manager fie...

Our organization often maps Master Features against Features as dependencies, and there is presently no way to do analytics on this data because the information is not available via API. Please expose.

What is the challenge? Identifying WHO is the lead on each workspace What is the impact? Efficiency in triaging questions Describe your idea On the features boards since we are largely using one PdM to one workspace- is there a way "Assign" a PdM ...

What is the challenge? I have two things that I need to be calculated using generally the same inputs. The calculations are completely different and we need to restrict what the person can enter and provide help text so we are using two separate s...

What is the challenge? An Example: Organisations can not be displayed on Ideas portals alongside the name of the person creating the Idea. Organisation data can also not be displayed in the portal ideas. What is the impact? When there are a lot of...

While many To Dos are simple and can be quickly marked off. Some could be longer and do not work as "requirements. Would be nice to set a start date and end date on a To Do and perhaps spark a notification reminder to "get started".

From a branding standpoint, it will be great if we can customize the logo on the login screen, instead of the default "Aha!" logo. THanks

We use a custom field at Idea level for sizing the efforts estimate of implementing a received idea. When we convert a selected idea into a feature, there should be an option to link this custom field to the Estimate field for Feature. This would ...

I would like to be able to limit use of an extension to a set of users. For example, if I have an extension to deploy code to production, I would like to limit it so that only an ops team and team leads can trigger it.