By default, have the Epic based data values copied over to the Feature data fields when the user creates a new feature from an epic card. This eliminates the need for re-entering and possibly inconsistent values for the same fields. If inherited f...
Guest
over 4 years ago
in Features
8
Future consideration
Dynamically create key results from key results field
What is the challenge?
As new tactical records are being input there are times where new key results are being defined. Today a user would need to go to the objective, then create the key result, then go back to the tactical record and associate...
Kristina Gass
3 months ago
in Strategy
0
Future consideration
Ability to collect feedback from users via a form/poll within your Aha! account
What is the challenge?
A way to consistently gather usability feedback from users
What is the impact?
Users share usability challenges in email, IMs or sometimes in meetings (Data is inconsistent)
Describe your idea
A feature that ca...
Edgar Holguin
3 months ago
in Backlogs
0
Future consideration
Collapsible sections/headings in Notes to improve content creation & reading
What is the challenge?
Long notes become unwieldy to write, read, and edit. This makes it difficult to review, consume and share detailed content.
What is the impact?
The lack of collapsible sections and document navigation menu means one ...
Ian Babelon
3 months ago
in Notes
0
Future consideration
Add label dropdown select list when creating parent lines
Currently the only way to visualize multiple levels of goal or initiative rollups is to use the hierarchy report. Creating a hierarchy report can often be challenging because the labels used when creating parent lines are rarely defined to use con...
Jeanette Resnikoff
over 3 years ago
in
0
Future consideration
I'd like to be able to configure the status filter on the ideas portal to hide other statuses by default. For example, I'd like to hide ideas with the will not implement status from the default list of ideas.
Erin Ward
over 3 years ago
in Ideas portal
3
Future consideration
Allow removal of product value score column from prioritization view
Use case: there are times when I need to prioritize my list based on a custom scorecard that we've added as a custom field. It becomes hard to do this because I can't hide, remove or re-arrange the order of the product value score column.
Dale Potter
about 3 years ago
in
6
Future consideration
Copying an epic should also copy the associated features
Currently, if I want to copy a Master Feature, I must copy the Master Feature, then copy each associated Feature and map them to the Master Feature. This is time consuming and doesn't make a lot of sense.
doug evans
over 6 years ago
in Epics
10
Future consideration
Amount of changes made by a user when Account Level permissions
What is the challenge? Business Problem to Solve: Utilization report: We would like to know who is utilizing the Aha Account Level? How can we manage the amount of changes made by a user when Account Level permissions have been granted? License co...
Mike Jacobson
over 1 year ago
in Account settings
1
Future consideration
When using master releases, it is not possible to select the release template for the sub-releases to be created. Which means the workflow to date looks like this:
Create a master release
Resist the temptation to select the products in the produc...
Guest
about 10 years ago
in Releases
12
Future consideration