All ideas
Sort by:
Trending
Status:
Future consideration
Showing 6308
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
1
VOTE
Auto disable Users when their Okta account is disabled
What is the challenge? When users leave the company and their Okta accounts are disable, their Aha user accounts remain active What is the impact? This impacts our available user license count in Aha Describe your idea Improve the Okta integration...
0
Future consideration
3
VOTE
Filter or only show items relevant when linking
Who would benefit? All user of Aha What impact would it make? Would save a lot of time and make work load easier How should it work? When linking or merging ideas in Aha, the list presented should only show items that are relevant to that workspac...
0
Future consideration
3
VOTE
Add 'Convert to Key Result' to Whiteboard
Who would benefit? Solution managers, business leaders What impact would it make? Enrich OKR brainstorming sessions How should it work? We use an OKR canvas in an Aha! whiteboard to work objectives through to leading and lagging key results. Once ...
0
Future consideration
14
VOTE
New setting to allow ideas created in aha to default to public view
Currently, when an idea is created in Aha (not a portal), the default visibility is set to private. This has to be manually changed for every idea that is created. We want a configuration setting that will allow admins to change that to a Public v...
5
Future consideration
5
VOTE
Whiteboard timelines should match fiscal year setting of Aha! account
Who would benefit? Customers whose fiscal year does not align to the calendar year What impact would it make? Currently, the timeline shape available for whiteboards shows a quarterly breakdown, but for teams with fiscal year start that is not Jan...
1
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
53
VOTE
Expand/Collapse Release View to include Requirements
It's critical for our teams to see Features AND Requirements on the Release (Overview/Details View). You should be able to continue expanding down the hierarchy from Epic > Release > Feature > Requirement all within the Gantt.
7
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
2
VOTE
Add "Prioritization" to Releases
What is the challenge? I was actually trying to figure out a way to do this with a custom setup and noticed the prioritization screens for Features and Ideas. We need it for releases! What is the impact? Other than the order of the gantt chart and...
0
Future consideration