Application

I'm not sure why it's not possible to have features in release templates. Phases and milestones are nice, but features are what actually have the status. This would be especially powerful for recurring releases. For example, I'm manually creating ...

When using filters in Features, Releases, or Roadmaps, dynamically show options that are relevant to what has been filtered. This is already implemented when using a workspaces filter and a specific workspace or group of workspaces is selected. Th...

Email is still the most used tool in business. ideas, project information, technical details... are all sent via internal email. Integrating Aha with email by using an add-on will be great. The user right-click on a message to see a sub-menu of Ah...

Who would benefit? Customers who need to display all types of record relationship in a whiteboard- not only dependencies. What impact would it make? It would allow teams to see parent/child relationships, blockers, and other types of record links ...

Our data model is such that every workspace in Aha! maps to a platform and we use a custom table to define the mapping. Since the field is mandatory for all objects in said workspace, we make the field mandatory when creating new features. We can'...

When I promote an Idea to a Feature, I would like to automatically set the Feature TYPE field based on information in the Idea record. The Idea CATEGORIES field is similar to the Feature TYPE, but multiple values can be selected for the CATEGORIES...

When user logs out of Aha! the logout message should be sent to the IdP. If user logs out of IdP Aha! should process logout message and also logout user. This should be supported for both Aha! and for idea portals.

What is the challenge? When users are disabled within the account, they are visible in list reports within the assigned to and user custom fields. The bulk edit function does not allow for the removal of these users in the report. What is the impa...

What is the challenge? Today, when searching on the features > board view Aha! only applies search to what is on the screen. When parking lots are being used and they have not all loaded yet they are not included in the original search results....

I have a mandatory custom field in Aha! Feature’s form and I would like the field to be non-editable once the release is approved through fixed workflow statuses, so that people could not make any changes there and any exception changes should go ...