All ideas
Sort by:
Trending
Status:
Showing 8948
7
VOTE
Story Map - don't move the feature off the map when it's assigned to a release
We find it very useful to view the entire story map with stakeholders throughout the development process and even into release planning and beyond. This often helps frame context of discussions for new features by being able to hop back to items a...
1
Future consideration
1
VOTE
Search ideas referencing proxy vote data
Who would benefit? internal and external users What impact would it make? save time, reduce duplication, improve discovery of the ideas How should it work? in ideas portal when searching and typing in the string - it should reference data in proxy...
0
Future consideration
1
VOTE
Add Additional Features to support Information Governance Requirements
Who would benefit? All Users What impact would it make? Satisfy Information Governance requirements by providing administrative control over record retention within Aha! services by providing administrators the ability to control the following: 1)...
0
Future consideration
1
VOTE
Auto-increment tag when selected for a number attribute should disable Minimum, Maximum, and Decimal input by the user
Who would benefit? End User What impact would it make? Manage expectations on how autoincrement works How should it work? Autoincrement tag for a number attribute when selected by the user should autoincrement by 1 and lots of other options should...
0
Future consideration
1
VOTE
Perform Automation Actions Against Fields not on Layout
Who would benefit? All Users, but especially administrators. What impact would it make? It would allow administrators to perform automations against records without the associated field ever being visible on the record. Reports also already suppor...
0
Future consideration
2
VOTE
please move overview back from strategy to an administrative or configuration area
My users did not connect the overview of the workspace to the strategic menu of ideation and strategy features. They still believe its part of a more administrative, configuration type of feature set as it was under the prior menu area. Can it be ...
0
Future consideration
2
VOTE
rework names and menus to be more user friendly or intuitive
My new Aha! users are consistently bewildered by the way the feature object and reporting object menus are positioned and named. Its always a first-hour training topic to explain the bad UX. What they would prefer is 2 different menus as your mast...
0
Future consideration
2
VOTE
Ability to hide record prefix
At the beginning of activities and initiatives, there is grey wording. For activities it numbers the tasks, for example, MARKETING-11. The prefix is used to create a permanent unique identifier to locate records throughout the database. However, o...
0
Future consideration
3
VOTE
New "integration reference" custom field type to house read-only text reference to a field on other side of Jira (or other) integration
There are fields in Jira (and I imagine other integrated applications) that don't map cleanly to an Aha custom field type. I am proposing a new custom field type that is an always-readonly text field that can be mapped to any Jira field type, and ...
0
Future consideration
3
VOTE
