All ideas
Sort by:
Trending
Status:
Showing 8930
4
VOTE
Quarterly Capacity Planning
Regarding Capacity Planning, we’d like to understand what can fit in an entire quarter and break down the deliveries monthly but some will be bigger items will not fit in each month and sit across a few. Therefore having monthly capacities is hard...
0
Future consideration
1
VOTE
Timestamps for Ideas Comments in New Ideas Portal Layout
Who would benefit? It would be beneficial for customers to be able to see a timestamp for when a comment was posted. Similar to what already exists in the Classic Ideas portal. What impact would it make? Keep comments more organized and digestible...
0
Future consideration
2
VOTE
Introduce additional options for "Next ..." filters in reports
Current process: Today, we can create reports that are filtered on: Last {week, month, quarter, year, 7, 30, 90, 180, or 365 days} This {week, month, quarter, or year} Next {week, month, or quarter} Product Gap: Our options for creating filters ba...
1
Future consideration
6
VOTE
Idea / request filter on domains not just portal users
I would like to be able to filter on the idea/request email domains associated to a portal user, rather than having to pick the individual names. If I use the idea voter domains I get a list of all domains, what I would like to see is the 'Idea/re...
0
Already exists
6
VOTE
Prevent Reviewers from changing the visibility of their own ideas
All my internal users are Reviewers, as I want them to be able to see more in depth information than they can get through the idea portal. However, I don't want anyone but an Owner to be able to mark and idea as Visible to Anyone. Internal employe...
0
Future consideration
8
VOTE
Paid Seat Transparency Across Aha! API
When calling get-all-users in the API we receive the field “paid_seat”. This field is not included in any other get-user calls inside the API, not specific user, or user by product. This is a problem. In February we had around 500 hundred users. W...
1
Unlikely to implement
8
VOTE
Master Feature release should be automatically established from Feature release info (i.e. inherit the last of the due dates of the features)
It is extremely inconvenient and the cause of much manual reconciliation that the Master Feature release (and date) isn't *automatically* established as the latest of the related Feature releases (and dates).
So can the Master Feature release rele...
1
Unlikely to implement
3
VOTE
Resize boxes on user story map to show all text for steps, epics and features
Currently the user story map does not resize the boxes for steps, epics and features to show all of the text. It would be helpful to be able to see all of the text for each box on the screen and when exporting to PNG, PDF, or a presentation.
0
Future consideration
8
VOTE
Add optional date fields or ranges on Requirements
Allow Requirements under features to have Date fields. These could be locked to the feature's date range or allowed to fall outside depending on the organization and how they manage.
This would allow for more granular reporting on Features, or t...
4
Unlikely to implement
6
VOTE
