All ideas
Sort by:
Trending
Status:
Future consideration
Showing 6239
8
VOTE
Automation: Allow an option to clear multi-value fields
At present, for Users-type custom fields, the automation options are: Add, Remove and 'Same As'.There is no easy way to remove all users. A 'Clear Values' option would be a great addition to Users field type and to other tagged field types.
3
Future consideration
3
VOTE
Add Automation Rules for Feature & Requirement To-Dos
Use Case: Based on a To-Do, there are additional automated steps necessary (i.e. Send Email or Make To-Do Comment). This could also be accomplished by have multiple triggers, such as Trigger: Assigned User is User A AND To-Do Status = Complete; Ac...
0
Future consideration
3
VOTE
Add Progress as Standard Requirement field/calculation
Add Progress field/calculation where user can select/configure whether it is based on Requirement To-Dos Complete or Estimated Hours/Actual Hours. We utilize Requirements to group tasks needed to complete a step of Product On-boarding, and we curr...
1
Future consideration
3
VOTE
Optimize searching and suggestion capabilities in ideas portals
Currently, the searching capabilities in the Aha ideas portal are seriously lacking. With better optimized searching capabilities, users (and internal employees) will find existing ideas more easily. This will optimize the user experience on our i...
2
Future consideration
18
VOTE
Allow Ability to Map Standard Fields to Custom Fields
We have a custom field for goals in the Idea ticket (where the requester must select which strategic goal their request ties to), but we can't map this field to the Goals field at the Feature level because they are both not custom fields.
We h...
4
Future consideration
9
VOTE
Have Workflow view respect release ranking from Features board
Currently the ranking in the Features Workflow board is not respecting the ranking from the Features Board. We use the workflow board for collaborating with the engineering team for planning and monitoring work. If we rank work in one board it is ...
1
Future consideration
16
VOTE
Option to hide select inherited personas at the product level
The desired use case to see supported is as follows: 1. Director of User Experience or Product Management creates (at the product line level) all possible personas for a product line.2. Each Product Owner then removes/hides (at the product level) ...
4
Future consideration
7
VOTE
Be able to select a default scenario for all users (Capacity Planning)
Right now, when you add a new scenario (even if it is just a test scenario), all users will be defaulted to that new scenario. We will have dozens of people using the tool, so the inability to get them to all set their own defaults to our standard...
0
Future consideration
11
VOTE
9
VOTE
Record Fields should create Relationships
Expected behavior when adding a Record field to a layout is that when records are selected, a relationship link is created. Use Case: We need to drive people to link specific records and leveraged Record Fields; i.e. one or more release, one or mo...
1
Future consideration