All ideas
Sort by:
Trending
Status:
Future consideration
Showing 6268
8
VOTE
Make priority limit line dynamic on prioritization views
I would like to specify the metrics that automatically set the priority limit line on the prioritization view. For example, if I know that my estimate limit for a list of records is 100d, I would like the priority line to dynamically set/adjust ba...
2
Future consideration
12
VOTE
Allow Enterprise Customers to Manage Account Upgrade Advertisement Pop-up messages
Enterprise accounts are managed through centralized procurement processes. It is inappropriate and confusing for Aha! to be advertising a Free trial to individual users to enable Ideas Advanced features. It would be useful to have an instance-wide...
0
Future consideration
51
VOTE
Ability to hide colums from list view when using Calculation columns
New Calculation column in List view is a great improvement. When creating List reports it would help to make the report more 'clean' if you could hide the source columns from the report and only show the Calculated columns. This would be similar f...
3
Future consideration
73
VOTE
Unique field layout based on feature type
As we continue to expand our use of Aha, one issue that has come up is that within a given product, there are different types of work/requirements that require different types of information. We're adding more and more custom fields, and it's star...
8
Future consideration
7
VOTE
Allow Workspace templates to inherit layouts from product line
Who would benefit? Anyone who wants to use a workspace template for things like automation, but wants to use product line inheritance for layout configuration. Our automations are able to improve data quality and reduce administrative overhead for...
0
Future consideration
19
VOTE
Make the standard tags field mappable for requirements
Both epics and features have the standard tags field mappable when setting up an integration. Requirements now have a standard tags field added to the record but it is not available in the mappings. It currently requires a custom field be created ...
1
Future consideration
17
VOTE
4
VOTE
Make it easy to prioritize a body of work's child records
Who would benefit? Teams who need to ensure clear prioritization on the subtasks within a body of work. What impact would it make? Right now, the only way to filter, for example, the features prioritization page to a specific body of work, is usin...
0
Future consideration
11
VOTE
Support updating JIRA Integration Links by csv upload
While I recognise that moving JIRA issues between projects breaks the AHA integration links, the workarounds proposed here are not helpful. Option 1 ("Relink each record manually") is the only viable workaround, with options 2 and 3 being too haza...
0
Future consideration
41
VOTE
Add 2-way integration mapping for release start and end dates
Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...
2
Future consideration