Application
Sort by:
Trending
Status:
Future consideration
Showing 7522
4
VOTE
Knowledge base page publishes automatically once approved
What is the challenge? We want KB pages to be approved before they are published. What is the impact? It is a manual process right now and we have to trust users that they will not publish a page before all the approvals have been given. Describe ...
2
Future consideration
8
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
24
VOTE
Allow formatting and wrapping text on chart labels
I never use Aha charts in our internal reports because the labels display poorly. It's a shame, because it prevents our org from more fully adopting Aha. I export everything to do reporting in a Spreadsheet simply because the labels are unhelpful ...
2
Future consideration
53
VOTE
Report on a values historic values
Enable the user to report on the values of a field based on its history. maybe a calculated field property where you indicate the field and the version back for that field. History(Custom_Field1,1) would show the value of that field one change bac...
5
Future consideration
13
VOTE
Show more context for added/removed records in retrospective report
I want to understand more about the records that are added to or removed from a release: When was it removed? Where was it moved to? What is its current status? I would like to see this information in the retrospective report
1
Future consideration
85
VOTE
Don't remove lane in feature board view once shipped
Currently when you ship a release the lane disappears from the feature board view. It would be great if instead of disappearing all together the lane was simply greyed out or marked as shipped. The feature board view is where we look to see what w...
26
Unlikely to implement
8
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
12
VOTE
Dependency roadmap as a standard view
Who would benefit? Users that: need to track upstream work they are dependent on need to understand downstream work that is dependent on their work need to easily identify delivery risks based on dependencies What impact would it make? A roadmap i...
0
Future consideration
10
VOTE
Allow Release Date (internal) and Release End date (date range) to sync
Who would benefit? The Release date (internal) drives many of the OOTB reporting functionality in Aha! so it must be maintained and accurate for reporting to be accurate. For many teams, the end date of the release and the Release date (internal) ...
1
Future consideration
5
VOTE
Ability to set Auto-refresh schedule
What is the challenge? Currently, when we view a shared webpage, it takes a while for the refresh to complete. At this point we have already started reading the webpage and once the refresh completes, we lose our place where we are currently readi...
2
Future consideration