All ideas
Sort by:
Trending
Filter by:
Status
Showing 9004 of 9004
1
VOTE
New requirements that are created under a parent feature that is already in the prioritized backlog should automatically be placed in the prioritized backlog.
What is the challenge? New requirements that are created under a parent feature that is placed in the prioritized backlog is placed in another area of the workboard. The user then has to find the new requirement and move it to the prioritized back...
0
Future consideration
1
VOTE
When creating a new requirement under an existing feature we would like the option of assigning the requirement.
What is the challenge? Sometimes a feature will be assigned to a developer and another developer creates a requirement under the same feature and starts working on it. Today the new requirement will automatically be assigned to the same person the...
0
Already exists
1
VOTE
Subscription model with a possible Aha! listener
What is the challenge? We have a scenario wherein Github is becoming Single Source of Truth for any changes. Our idea is that can Aha! have a listener. Listener will listen to any changes in Github. this will help changes in Aha! maintained. this ...
0
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
3
VOTE
On Feature Roadmaps, I would like to be able to hide individual epics shown at the top so that i can share features with a key identifying which epic they belong to while retaining the ability to hide epics I don't want to include in customer facing information.
Who would benefit? Product Owners What impact would it make? Better control of messaging and content How should it work? When you choose to include Epics on a Feature level roadmap, you can hide features by hovering over them and selecting the hid...
0
Future consideration
3
VOTE
Add Merged Idea as a field in automation rules
Who would benefit? All Aha users. What impact would it make? In my specific use case we have started adding to-do automation for the assignee when an idea changes status to remind them to update the admin note on the idea. When this happens a to-d...
0
Future consideration
4
VOTE
Default settings for saving reports
It would be great to have default settings for saving reports. For example: the ability to assign reports to share internally with and into specific folders (as opposed to saving generally) by default. All reports created in workspace X would be s...
0
Future consideration
23
VOTE
Add Burndown Chart for Initiatives
We're adopting a more flexible release strategy that is feature/initiative driven, not time boxed. It would be great to be able to generate a burndown chart for an initiative (even better: overlay several initiatives) so we can project/monitor our...
1
Future consideration
23
VOTE
© 2024 Aha! Labs Inc.•All rights reserved