All ideas
Sort by:
Trending
Filter by:
Status
Showing 9694 of 9694
1
VOTE
DevOps Integration: button to receive all fields
What is the challenge? Possibility to easily refresh an item from DevOps What is the impact? In case of non-synchronized items, it will be easier to refresh the status from DevOps Describe your idea Currently, when an item is linked to a correspon...
0
Future consideration
1
VOTE
Log time on behalf of other user via API
What is the challenge? As we track the time using another tool, we would like this to be imported in Aha via API, with the appropriate user assigned What is the impact? This will make it possible to have proper time logging in Aha as well without ...
0
Future consideration
7
VOTE
Add Release or Parking Lot info to Initiative Features
Currently when you open an Initiative, the “Features” section lists all the features in the initiative along with the feature status, but nothing about “when” it is going to be done. That feature grid should have a column showing “Release” to disp...
2
Future consideration
7
VOTE
1
VOTE
Add Requirements and other records with terminology to My Work "Records" section
What is the challenge? Users are unable to view Requirements (or Tasks in our environment) when viewing the My Work tab alongside other records they are assigned. What is the impact? Users find it more difficult to find the requirements/tasks that...
0
Future consideration
1
VOTE
Customize Documents header
What is the challenge? Currently, Aha Document headers are not customizable and default to "[workspace terminology] documents." What is the impact? Being able to customize the header would provide clarity on which workspace a user is in. Describe ...
0
Future consideration
1
VOTE
Allow users to disable "Move features to new release" popup
What is the challenge? When moving an Epic between releases, in our solution workspace, a popup asks "The following feature will be moved to NEXT. Please indicate whether the non-shipped epics in this feature should also be moved." Accepting moves...
0
Future consideration
3
VOTE
4
VOTE
Integration with JIRA needs better Error handling support
Aha! integration with JIRA does not notify users on errors that would have happened during the integration (i.e. push/pull). This keeps the users in dark on what would have gone wrong and requires manual intervention to detect errors.
1
Future consideration
3
VOTE
Provide the ability to map the Release field from a Feature or Epic to an external system such as ADO
Given that AHA is all about releases and ADO is all about time lines, the concept of a Release in AHA is quite different than what exist in ADO - yet there is a Target Release field in ADO as well as in the Feature of AHA - please can this be expo...
1
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved