Application
Sort by:
Trending
Status:
Future consideration
Showing 7522
5
VOTE
Enable filtering records on related tab by the workflow status rather than status category
What is the challenge? Filtering on related items is based on the Aha category of status, not the custom workflow status of the workspaces, limiting our ability to filter what we want to view in related items What is the impact? This limits our ab...
0
Future consideration
6
VOTE
Reference key results in worksheet equations
Who would benefit? Everyone tracking OKRs in Aha! Roadmaps What impact would it make? Allow teams to leverage the power of worksheets to perform custom calculations on their key result data How should it work? Support referencing key results in wo...
0
Future consideration
6
VOTE
Customize the "Key results" table on the Related tab
Who would benefit? Everyone tracking OKRs in Aha! Roadmaps What impact would it make? Allow me to customize the key result data displayed on my records How should it work? Ability to customize the "Key results" table on the Related tab
1
Future consideration
106
VOTE
Better pagination for PDF presentations
Some of my stakeholders would would prefer to printed presentations, but the PDF rendering engine does not do a great job of pagination and I am a bit embarrassed to share a PDF. Currently, each presentation "view" starts on a new page. This looks...
4
Future consideration
5
VOTE
Option to include reference number in subject of email notifications
What is the challenge? For our users who transitioned from Jira to Aha, they are struggling with reduced efficiencies due to th efact that email notifications from Jira included the reference number in the subject while Aha only says "[AHA] Recent...
0
Future consideration
6
VOTE
If you link an initiative to an epic, it would be nice the features linked to the epic are automatically linked to the initiative
Who would benefit? Product owners What impact would it make? Less manual work How should it work? Link epic to an initiative Pop up to link the features as well (cfr when you move an epic to another release) Without use of automation rule (no ente...
0
Future consideration
38
VOTE
Inherit field values from Epics to Features
By default, have the Epic based data values copied over to the Feature data fields when the user creates a new feature from an epic card. This eliminates the need for re-entering and possibly inconsistent values for the same fields. If inherited f...
7
Future consideration
85
VOTE
Allow sorting records in custom tables
Custom table records are currently sorted by order of creation. Since users often create more important/common records first, the important ones end up at the bottom of the list. Instead, allow sorting these records via drag-and-drop (or at least ...
14
Future consideration
70
VOTE
Connected Tableau with Aha! for external reporting
As Aha! reporting features are not advanced / flexible enough to meet all our data analysis requirements, it'll help if it is possible to connect Tableau with Aha! directly so that we could handle the analysis by ourselves.
More importantly, Tabl...
3
Unlikely to implement
51
VOTE
