All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5672
4
VOTE
Assignee of feature in Aha! should propagate to Gitlab
As a user of Aha! / Gitlab integration, I would like to assign a feature in Aha to a specific user and have it show up as assigned to them in Gitlab, so that they are aware of the new feature and can take responsibility to break it down further in...
0
Future consideration
2
VOTE
Allow Jira-related fields to be included in automation rules
It would be helpful for fields like the Jira key or integration link to be available in automation rules. That would enable my team to create triggers that look at when an integration link is changed or is no longer available.
0
Future consideration
2
VOTE
Allow for null Release Date
Currently the release date field is required. But usually when a release is first written up there is no realistic idea for when it might be delivered. For releases that are postponed or of lower priority, the initial entered dates which seemed so...
0
Future consideration
3
VOTE
improved metadata rest services for fields
For users trying to interface with the Aha service via the rest services there is a definite lack of available services for fields.
There needs to be a way to validate fields being sent to Aha. Currently there are only services that return filed d...
1
Future consideration
3
VOTE
Apply Template when creating Release from the Master Release
When creating a child release from the master release, allow the user to apply a product template to the created release. This will allow the Sub-Release to have all of the steps etc. required. Currently, the user either needs to create the releas...
0
Future consideration
2
VOTE
Sync Sprints betweeen Aha! and Rally
As product owners use Aha as the primary repository to develop and track their roadmap, they want to enhance their planning phase by improving the existing configuration between Aha and Rally. Currently, capabilities, features, and user stories ar...
0
Future consideration
1
VOTE
BUG: Deadspace on Custom Pages for Ideas Advanced Users
There is a tremendous amount of dead-space (unused pixel real estate) on custom pages. More than 50% of custom pages are not displaying page information. This leads to squished information that requires horizontal scrolling to view all the informa...
1
Future consideration
1
VOTE
Grant Workspace Owners the ability to manage Ideas Advanced Portal
We purchased Ideas Advanced Portals. With this purchase, we would expect the ability to share ownership/management of the portals created with business users (in the workspace owner role). These business users should have access to manage their id...
0
Future consideration
2
VOTE
Allow child releases for a master release to retain unique names
There are instances where multiple releases exist within the same product workspace that are separated intentionally for visual management. Creating a rollup release causes the children to inherit the parents name, but it would be useful for the c...
0
Future consideration
2
VOTE
Have linked releases to goals and initiatives only show work related to that container
Currently the linked releases to an initiative or goal, show all complete and pending stories for the release. If a release is not 1:1 with the initiative or goal, those items are showing work that is not related which gives a false perception to ...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved