Account settings
Sort by:
Trending
Status:
Showing 647
3
VOTE
Ability to create custom fields with context
When we create custom field in AHA we want the ability to create context for each product so that we can see only values which are relevant to a specific product. For example Team A, Team B and Team C are related to Product 1, we do not want to se...
0
Already exists
1
VOTE
Calculate progress based on completed status of child records
I would like the option for Aha to automatically calculate the progress of an Initiative based on the number of Epics or Features that are Released verse still open. The same would apply to Epics and the child features.
2
Future consideration
1
VOTE
Automation - add specific data range when choosing time frame
When creating an automation for a goal, it would be nice if I could add a specific date after choosing a time frame. So if I create a new goal, and choose a time frame of FY23 Q3, I'd like to set a custom field Goal Start Date as Oct 1 and a custo...
0
Future consideration
2
VOTE
Assign Custom fields to a parent workspace
We have over 250+ custom fields being utilized by various workspaces. Because we cannot assign a custom field to a particular workspace all 250+ fields are visible in every filter in every workspace. If we could have the ability to define which wo...
4
Future consideration
4
VOTE
Ability to suppress Product Line level custom fields from products
We have some custom fields that we want only to appear at the Product Line level, specifically for Master Releases and PL Initiatives. We'd like a way for them not to appear in Product Initiatives or Releases. As it stands now we just need to inst...
0
Already exists
2
VOTE
Inconsistent / Broken Terminology
Within Marketing, Business and Project Lines, the customize terminology setting is broken and creates an inconsistent user experience that confuses users. Within the 'Customize Terminology' setting (Settings > Product Line > Terminology), if...
0
Future consideration
1
VOTE
Product line prefix for all ideas of all product workspaces under it
Let's consider an example to understand it better: I have a product line called: "Line1" having a prefix as "L1" I have 2 product workspaces under the same product line, i.e., Product A with prefix as "PA" Product B with prefix as "PB" I have an i...
0
Future consideration
2
VOTE
Line and Workspace management - stop collapsing the Line / Workspace hierarchy each time you complete a Line
If we leverage UX / UI, when a user-persona leaves a data structure in a window, they should expect it to remain the way they left it when they return, or complete a task Currently, when I go to the Customized Workspaces --> then expand some or...
0
Future consideration
2
VOTE
Opening 2-factor authentication to other providers
aha!'s 2-factor authentication implies signing up with a designated 3rd party. We would like to include aha! with the other solutions in our IT portfolio, for which 2-factor authentication is supported by a different supplier than aha!'s partner.
1
Future consideration
1
VOTE
In-app requests for workspace roles
It would be great if users with access to workspace could submit a request within Aha Roadmaps for a different role to be assigned to them or for a role to be assigned to other users. This would streamline the process for admins to assign roles to...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved