My ideas: To-dos

What is the challenge? When a workspace name is excessively long, it overlaps and pushes the right-side navigation menu items out of view in the top toolbar. There is no horizontal scroll available, so affected items like the Settings icon become ...

What is the challenge? New conditional choice fields are not supported in automation rules. What is the impact? Unable to create rules based on choice field values. Describe your idea. Show choice field options when setting up automation rules.

What is the challenge? When users want to use Comment Templates, they have to rely on the Comment Template name as text given on the tile displayed is not readable. What is the impact? Ease of use when using templates as it is having great benefi...

What is the challenge? Only Aha! owners/contributors can use the MCP server connection What is the impact? Limits the scope of use of the MCP server Describe your idea. Enable the MCP server to work similar to the Aha! REST API with user permiss...

What is the challenge? Creating and maintaining related links is a manual process. When a field on an epic is set or updated, the user must remember to navigate to its Related tab and manually add the corresponding link, which is time consuming an...

What is the challenge? The goal is to create a roadmap view with multiple record types as bars, nested/collapsable, with custom fields and color coding baed on custom fields. The Custom roadmap provides for custom fields and color coding but n...

What is the challenge? It is possible to pull data from the organization[s] related to a proxy vote to either the proxy vote or the idea via a custom worksheet. It is not currently possible to pull organization info from direct votes or idea submi...

What is the challenge? Currently, you cannot import requirement start/end date (date range) values via CSV What is the impact? Manual effort to update date ranges and cannot use the standard date range functionality with requirements. It is much ...

It's currently not possible to import release phase custom fields via CSV or access them via API, unlike other record types.

Currently only Aha! users that create an idea can be sent to Jira using the Created By User field. Given that many ideas are created by ideas portal users that are not Aha! users, it would be desirable to be able to send these users' email address...