Instead of listing features within the same epic in alphabetical order, it would be helpful to be able to rank features within epics, not only releases.
Amanda Chan
almost 2 years ago
in Epic
6
Future consideration
Show epics and features together on features board
By adding grouped features to the Master Feature view this would allow users to see which features are within their master features, and allow drag and drop of features between master features.
The display of features is currently not an optio...
Guest
about 4 years ago
in Epic
3
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 4 years ago
in Epic
8
Future consideration
Restrict the visibility of specific custom fields to different users
We use Aha! for all our product planning, however we currently do some financial estimates outside of Aha! which we don't want to share with the wider development team. This causes us to fragment our data and use permissions in other portals as th...
Mark Gerrard
almost 3 years ago
in Epic
5
Future consideration
Estimate field defaultable to 'Calculated From Features'
We want all of our features' estimates to roll up to their epics. As it is now, when we create new epics, we need to go and set that and it gets missed a lot.
Guest
over 5 years ago
in Epic
6
Future consideration
When viewing the details of an initiative (or master feature), it would be helpful to see the child-master features (or features) sorted by priority order rather than alphabetical order. That way, the child records wouldn't necessarily have to be ...
Guest
over 4 years ago
in Epic
0
Future consideration
In my Aha boards, I have epics/projects that have "related" features/activities. One thing I have found is that it can be difficult to see details for the lower level features/activities without going into the ticket itself. Under activities in th...
Guest
about 2 years ago
in Epic
3
Future consideration
We use Master Features a few different ways:
A group of related features
A use case that requires work (features) from different products.
A feature that will be implemented in different products at different times (each of those would be a...
Julia Doyle
almost 5 years ago
in Epic
1
Future consideration
Automation rule to set a manually calculated progress field = 100% when status category is set to done
I like the agile rule of done or not done with an between status of in progress. So when I indicate the record is done and the progress field is manually calculated, it would be efficient to set progress field 100% complete.
Richard M
over 3 years ago
in Epic
3
Future consideration
When adding features to an epic, I should be able to select multiple Features
When creating an epic, that has features that already exist. Its not possible to add more than one at one time. This means that each time I want to associate a feature, I have to open the select "Add" then the modal will appear to select existing ...
Andrew Brooks
over 2 years ago
in Epic
0
Future consideration