Greater functionality for idea portal automations used with multiple selection fields
We use automations to automatically assign ideas based on their categorization. Quite often ideas overlap product categories and as such multiple categories are assigned. The issue we are finding is that by adding the secondary categorization the ...
Dan Green
about 4 years ago
in Ideas portal
0
Future consideration
I often embed Aha shared webpages in Confluence and Notion. These apps require me to give a name to the page which is often the same as the name I give to the note or roadmap that I embed in the page. This results in the same name appearing on the...
Heather Phagan
about 2 years ago
in Roadmaps
0
Future consideration
Allow Idea viewer to update proxy votes (not raised by you)
As it currently stands Idea viewers are not able to update votes, which were not raised by them. There are multiple reasons why the viewer may want to update existing votes: 1) reflect the latest severity / impact (e.g. downgrade / upgrade) 2) mod...
Ros Bayev
about 2 years ago
in Voting
0
Future consideration
We archive ideas that are over a year old and have not received any votes to simplify our internal research. In most cases, these Ideas are already marked Will Not Do, so our customers don't need another notification that we're still not doing it....
Lee Jacobs
about 2 years ago
in Ideas portal
2
Already exists
Ability to remove large new obtrusive Icon on feature cards to indicate Jira Integration
A very large icon has been added to the Aha feature cards to represent Jira integrations. Previously, the Jira reference number was shown as a hyperlink. The new icon has significantly increased the size of each feature card with no benefit and ha...
Melissa Hughes
about 4 years ago
in Features
2
Already exists
Allow multiple Zendesk tickets to be linked to more than one Aha idea (when creator is the same)
For our customer base, we're finding that users are asking for the same thing in multiple tickets, or couching similar requests in multiple tickets. However, when I got to link it to an existing idea (to keep our ideas clean), I get an error messa...
Kaitlyn Moore
about 8 years ago
in Ideas
1
Will not implement
When working with high level initiatives that span many quarters, current view demands lot of scrolling (using Quarter resolution). The quarter scale shoud be compresses to allow the full span view in a single page ideally.
Guest
about 8 years ago
in Features
0
Already exists
Label the description box on the feature details panel.
When we create a new feature we populate the box labelled description which is mapped to description in JIRA - the user story. . But in the detailed view in AHA! that description text appears in a blank box. Are we able to label this description?
Guest
about 8 years ago
in Features
1
Unlikely to implement
Reporting field for 'Initial Estimate' when 'Use tasks estimates' toggled OFF
When the Feature Estimate field is initially set (t-shirt sizing / SWAG), and the 'Use tasks estimates' configuration is toggled to OFF, an 'Initial Estimate' value is displayed for the Feature. When child Requirements are added, with the Requirem...
David O'Hare
about 4 years ago
in Features
0
Future consideration
The default view for Goals and Initiatives is the quadrant / scoring view; it would be nice to be able to default (at either the Account or User level) to the Detail view which is far more useful.
Guest
about 6 years ago
in Strategy
0
Unlikely to implement