Application
Sort by:
Trending
Status:
Future consideration
Showing 7647
13
VOTE
Coalesce common dependencies in the dependency map
Right now, I have a task which depends on several other tasks, and some ofthose depend on the same underlying tasks. An example of this would looklike:
A / | \B | C \ | / D
I would expect the dependency map view to draw a line between B&D as ...
0
Unlikely to implement
1
VOTE
Use AI to build segments for organizations
What is the challenge? Understanding ideas based on organization segments. What is the impact? Using AI to build segments could potentially surface connections between organization attributes. Allowing for better understanding of different market ...
0
Future consideration
1
VOTE
Ability to list users who are using API Keys
What is the challenge? Users have generated API Keys to update Aha and the Account Admins would like to know which users are using API Keys. What is the impact? How can we know who is updating using an API and understanding where the API is used t...
0
Future consideration
2
VOTE
Allow users to delete their Aha! account
It seems that atm when a user (idea creator) wishes to remove his user from Aha! he can't do it without contacting the Aha! support team and they have to contact the ideas portal owner (us) to remove and delete the user. Why not have this opting i...
1
Already exists
4
VOTE
Add a description within a report
I have a couple of reports which look for errors or omissions, and will be blank if everything is good. I would like to add a little text to the reports to explain that if it's blank, they should be happy, not contact me to ask if the report is wo...
0
Future consideration
7
VOTE
8
VOTE
Improve Reporting > Reuse Tables (Recursive Join)
Wholistic reporting in Aha is nearly impossible to do in a simple, and easy way. For example, when reporting on Ideas, if one would like to see the Release of each Idea where your Ideas may be promoted to Features or Master Features two reports ar...
1
Future consideration
15
VOTE
7
VOTE
Add configuration to link a Feature's Release to that of the Epic it is created in.
As a user creating (or integrating) a Feature under an Epic, I want to configure if the Feature will inherit the Epic Release, so that I can automate my Release scope when I create (or integrate from JIRA) a new Feature in an Epic. This will help ...
1
Future consideration
11
VOTE
Ability to create pre-populated custom fields
Our Use Case
We have a process that we've actually implemented as a product within Aha! that helps us track Change Requests. We set it up as a separate product within Aha! because this process has a different workflow that we wanted to capture, in...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved