We deliver customer solutions on top of our base product which often drive the development of (future) features in our base product. Because we have to manage these features separately as part of delivery of this customer "product", we then find w...
Ability to convert text field to note field in custom fields/layouts
We would like to be able to convert a text-based field to a note-based field in custom layouts by editing the field. Use case: We set up a set of fields to build a report, and one field (path to green) is a text field. We've since realised that th...
Nerissa Muijs
over 3 years ago
in Epics
0
Already exists
Ability to create custom drop down with values from another custom field in another workspace
I would like to create a custom drop down field that appears on all Epics that use a shared layout. The custom field should be the available values in another custom field for a specific workspace. To illustrate: * On workspaces 1-10, I want to ad...
Mike Lange
over 3 years ago
in Epics
0
Future consideration
Aha! Develop allows teams to have a unique layout for features and requirements. This helps them see the information they need for development, while hiding the information they don't. Please support this for epics as well.
Jeff Tucker
over 3 years ago
in Backlogs / Epics
0
Will not implement
I have a solution A which is made up of features X and Y from products B and C respectively.
However, X and Y may also be features in solution B.
With the recent update, you’re able to view master features along with features on the feature boar...
Guest
over 7 years ago
in Epics
0
Will not implement
It would be really great if the progress bar could be colour coded so that for each feature against an epic its status could be represented in its individual colour becoming progressively dark green as it more features are completed
Mark Colonnese
almost 4 years ago
in Epics
0
Future consideration
Visually represent the size of a feature with larger or smaller cards
In Aha, it's difficult to represent the relative effort required for different master features and features. Time is not the only consideration. For example, so features have dependencies that while not requiring heavy effort, will effect the dura...
Nate Dunlevy
over 7 years ago
in Epics
1
Unlikely to implement
We have 20+ people in Contributor role working on the same Product. All of them have by design access to bulk actions and can inadvertably bulk delete all of the hundreds of items that we have in Aha!. We want to somehow restrict access to bulk ac...
Guest
over 7 years ago
in Epics
0
Unlikely to implement
The customer success team suggested I just use initiatives for user journeys and master features for user journey steps, which is a good temporary fix. However, defining a user journey is a pretty specific thing that I think should be set apart fr...
Mike Mitchell
about 8 years ago
in Epics
2
Unlikely to implement