Application
Sort by:
Trending
Status:
Future consideration
Showing 7564
6
VOTE
Submit-only portal users to receive notifications for status changes
Currently submit-only portal allows only notifications to comments. We are unable to notify users or subscribers on status changes automatically. We need to manually enter comments regarding the status to inform them. It would be helpful to have '...
0
Future consideration
1
VOTE
Allow "To-dos" to support both Aha users and non-Aha users
What is the challenge? Representing actions where the assignee may or may not be an Aha! user What is the impact? To-dos are not usable for us otherwise Describe your idea Allow the input of an assignee who may not have an Aha account and show it ...
3
Future consideration
2
VOTE
Allow Portal Users to switch already posted comments to private
Who would benefit? Aha customers with strict governance What impact would it make? Allows employees to correct their mistake if they posted a public comment that should be private How should it work? When viewing comments in the portal, allow port...
0
Future consideration
2
VOTE
Ability for portal users to flag a comment as inappropriate
Who would benefit? Aha Customers with strict governance What impact would it make? Crowd-source moderation How should it work? When viewing comments in the portal, a portal user should be able to flag a comment as inappropriate. This would then tr...
0
Future consideration
6
VOTE
Aha! Develop: Split an individual's work schedule between 2 teams for capacity planning
My goal is to split a person's time between 2 teams (50/50). I'd like to have a schedule per team, so that I can indicate the days (or % of their time) they'll work on each team. Currently there is one schedule per individual, which is shared by a...
0
Future consideration
18
VOTE
5
VOTE
Allow conversion of Epic to Feature when the Epic contains features
When an Epic has no child features, you can convert it to a Feature. When an Epic has child features, today you cannot convert it to Feature. It would be a smoother workflow to allow Epics with child features to be converted to a Feature
0
Future consideration
2
VOTE
Increase the maximum number of records returned by the API
Who would benefit? Users who are using the API to build reporting out of Aha! (e.g. Power BI) What impact would it make? It would reduce the number of API calls that need to be made to retrieve large amount of records How should it work? Instead o...
0
Future consideration
2
VOTE
Allow sorting pivots by other fields when only description is displayed
When creating a pivot report and using the description field of our release phases to group records as columns, we are unable to select another field to drive the sort order. The application only allows us to sort alphabetically by the description...
0
Future consideration
4
VOTE
