All ideas
Sort by:
Trending
Status:
Showing 8935
21
VOTE
Hierarchy Report: Support Initiatives that have both Master Feature and Features in same report.
Right now if you create a report that shows Initiative/Master Feature/Feature, for features that are directly linked to the initiative they show as if they have no initiative associated to them. I expect those features to show in line with the ini...
1
Future consideration
1
VOTE
Ability to format (add a WYSIWYG) column descriptions of Now, Next, Later roadmap
What is the challenge? I want to include hyperlinks and use bold and italic formatting to the column description of the Now, Next, Later roadmap so we can emphasize certain things and create links to related documentation. What is the impact? This...
0
Future consideration
2
VOTE
Add indicator to reports when a "Default view" is being viewed
Who would benefit? Users utilizing "Default views" in their workspaces for multiple reports. What impact would it make? When clicking between different variants of similar views such as lists/pivots/charts, or pulling up many different reports in ...
0
Future consideration
12
VOTE
Configure AHA! to support GSuite - sheets, slides, docs, etc.
We are a company that uses GSuite, this would allow us to pull data into our collaborative space and manipulate reports to personalize further than what AHA! current allows. Currently the inability to use AHA with GSuite causes delays and setbacks...
0
Future consideration
3
VOTE
Converting sticky notes to other record types should not bypass any required fields processes
When converting sticky notes in a whiteboard to other record types, we don't want users to be able to bypass required field entry for those record types. I have found other areas within Aha! where required field entry can be bypassed when creating...
0
Future consideration
3
VOTE
Add better error handling for 'unhandled error exceptions'
When using AHA to integrate with other platforms such as Jira, sometimes fields are not mapped correctly due to either changes in Jira or custom fields in AHA. When this mismatch happens, we are only presented with 'unhandled error exception. Plea...
0
Future consideration
12
VOTE
Efficient removal of scenarios from capacity planning for teams
After having completed planning with the use of various scenarios (with capacity planning for teams), I would have narrowed down my optimal scenario and would want to remove or archive scenarios that are no longer needed. Currently to delete a sce...
0
Future consideration
11
VOTE
Personas can be 'mentioned' using # in a text editor
As a #productmanager, I would like to easily use a # to reference personas when I am defining a feature. This would work just as it does when using a # to refer to features or epics - typing #persona_name would search and find that persona. A litt...
3
Future consideration
2
VOTE
Nest or group to-do items together
Who would benefit? PMs, Product Ops, docs team, What impact would it make? Easier to use and navigate to-do lists within discrete phases How should it work? I'd like to be able to nest or group to-do checklist items under a higher-level checklist ...
0
Future consideration
2
VOTE
Ability for submitter to "flag" an Idea as a potential duplicate
Who would benefit? Submitters and Triage Team, everyone who wants to minimize duplicate Ideas What impact would it make? Enhancements to the duplication ID and merging process How should it work? A flag button someone can click if they think the I...
0
Future consideration