Application
Sort by:
Trending
Status:
Future consideration
Showing 7641
3
VOTE
Convert the results of the capacity report into another UOM or allow export of capacity report data
What is the challenge? The capacity report is great at showing your team's and/or user's capacity month by month, and highlighting any capacity conflicts. However, you sometimes want to view your capacity in different ways. For example the report ...
0
Future consideration
7
VOTE
Support named ranges with points as the base unit
What is the challenge? Named ranges require users to set ranges corresponding to time estimates. However, many teams use points as their common way of estimating. T-shirt sizes will correspond to a range of points. Points are also what come back a...
0
Future consideration
80
VOTE
Password protection for "Share as webpage"
Previously, we heavily used the "notebooks" feature to publish a scrollable webpage view of our feature lists for our Engineering teams that we didn't want to give access to our main Aha account. Now that "notebooks" have morphed into "presentatio...
21
Future consideration
3
VOTE
Support "same as" automations for custom text fields
What is the challenge? Automations currently make it possible to pass values from one record to another, such as users and dates. We need the ability to copy simple text fields (not note fields) across records. What is the impact? We need to captu...
0
Future consideration
7
VOTE
Allow @mention in Note field
What is the challenge? We use the 'Note' field throughout our record types, including Goals, Initiatives, Features, Requirements, etc. While we can use To-Dos, it would be easier for many of our use cases to @mention someone directly in the field ...
2
Future consideration
7
VOTE
Promoting an idea should copy the creator's information to the feature
What is the challenge? Currently, the "Created By" field on the idea card in Aha! displays only the name of the user who submitted the idea. However, this information is lost when the idea is promoted to a feature/epic, making it difficult to trac...
1
Future consideration
11
VOTE
Provide additional formatting controls to the Now, Next, Later Roadmap view, similar to Pivot Chart functionality
Who would benefit? Any user who is using the Now, Next, Later roadmap, or those who are creating their own version with a Pivot table. What impact would it make? It would allow users to more fully customize Now, Next, Later roadmap view to tailor ...
2
Future consideration
3
VOTE
link whiteboard object (x,y) position with field values
What is the challenge? When using a cost-benefit whiteboard to prioritize features it would be very helpful if the position i move a feature to was persisted to the feature card. What is the impact? This would make whiteboards part of actual work ...
3
Future consideration
15
VOTE
Automation of feature to another release based on custom field
Who would benefit? Product Management Team What impact would it make? Ability to cut down on manual work, reducing mistakes and time spent on administrative work How should it work? Under automations, be able to set a rule as such: When a feature ...
2
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 &...
14
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved