My votes
Sort by:
Trending
Status:
Future consideration
Showing 6307
43
VOTE
Time-based triggers for automations
Automations offer great potential to alert owners/interested parties of action, but are frustratingly limited by the absence of a time based trigger. In our case we want to conform to an SLA in processing ideas we receive and actively sending a re...
4
Future consideration
5
VOTE
Add ability to define timeframe by multiple quarters for Now, Next, Later Roadmap
Who would benefit? Any user who is using the Now, Next, Later roadmap and defines their timeframes by quarter. What impact would it make? This would enable additional flexibility for more 'ambiguous' timeframes (i.e Next) How should it work? Allow...
2
Future consideration
5
VOTE
Add Key Results to Hierarchy Report
Who would benefit? Teams using OKRs that choose to associate work with Key Results rather than the Objectives What impact would it make? More logical display of strategy through the new OKR records in the Hierarchy report How should it work? Abili...
0
Future consideration
7
VOTE
Include automated idea scorecards in Ideas Advanced
Who would benefit? Anyone on the Ideas Advanced plan What impact would it make? Using the same Enterprise+ functionality available today, teams can automate the calculation of their scorecard metrics based on other idea attributes like vote counts...
0
Future consideration
1
VOTE
Reorder 'Now, Next, Later' roadmap
What is the challenge? I need my roadmap to mirror a Kanban priority board (also, Initiatives progress from left to right) What is the impact? Stakeholders are confused when my Initiatives view goes left to right, but my Now, Next, Later view goes...
0
Future consideration
1
VOTE
Include Views and Reports as linked records for workitems
What is the challenge? When managing context for workitems, especially on Initiative and Epic levels, I want to include reports and views as Linked records. Currently only Documents are available. What is the impact? Easier to create a 360 view an...
2
Future consideration
6
VOTE
Ability to Configure Epic View as Default for all workspace views (Board / Prioritization)
Who would benefit? Enterprises who maintain Epic only or use Epic as primary record type. What impact would it make? Reduce confusion. The teams are currently directed to feature view on the board and prioritization view by default. Per Aha concie...
0
Future consideration
79
VOTE
User Story Mapping for Features/Requirements
Admins should have the ability to chose which records are in the User Story Mapping. We structure Aha! so that User Stories are at the Requirement Level so it makes sense for us to view as Features/Requirements
We don't use Master Features &am...
14
Future consideration
6
VOTE
Better Email Update Notifications
Who would benefit? All users who are subscribed or watching features in Aha! and utilize email notifications What impact would it make? More informative notifications directly in the email without extra clicks or searching in the history of the fe...
0
Future consideration
6
VOTE
Add "Dependency Not Scheduled" as a Delivery Risk
Who would benefit? Users who have enabled the Delivery Risks feature What impact would it make? It would allow to immediately capture on a feature if there is a dependency on a body of work that has not been scheduled. How should it work? Add a fu...
0
Future consideration