All ideas
Sort by:
Trending
Filter by:
Status
Showing 8935 of 8935
1
VOTE
7
VOTE
Follow custom workspace line terminology when viewing Roll up to workspace goals
When a workspace line references its parent, the naming of that parent should match the parent level, not the workspace level. By not reflecting the customized terminology we are introducing layers of confusion for the team members who don’t spend...
1
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
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
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
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
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
23
VOTE
Salesforce Integration: Allow customization of terminology
Currently we can rename the title of the Salesforce widget. We can also customize all the text within the Ideas portal in Aha. For us, we want to use this connection but we don't want to call them ideas, but rather e.g. Requirements.
This is possi...
0
Future consideration
22
VOTE
