Would be great to have the progress bar not just calculate on some field completed, but also show as a sort of segmented progress bar, where you can see the percentage of items in another status category. This would allow to have in one view a cle...
Kristof Dewulf
almost 2 years ago
in Epic
0
Future consideration
The concept of favorites exists in many places in Aha! — favorite reports, favorite attachments, and even favorite notifications. One place I’ve realized that I’m really wanting this functionality is with the records themselves. I would love to be...
When viewing the list of features in the master features, we can see the feature name, with a link to open it, and its status. The status should be a dropdown to quickly change the status of each feature directly from the master feature.
Guest
almost 5 years ago
in Epic
0
Future consideration
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
12 months ago
in Epic
0
Future consideration
We use master features to define use cases that require work from multiple products. The features linked to the master feature come from those different products. However, we need the ability to put requirements on a master feature to be able to t...
Guest
almost 5 years ago
in Epic
0
Unlikely to implement
Option to hide goals and initiatives from selection on the Master Feature, Feature or Release
I would like the ability to mark a goal or initiative as complete/obsolete so that they are not available for selection on the Master Feature, Feature or Release. I know that you can do this via Archive, but the issue with this is on the reporting...
Amy Lackas
about 4 years ago
in Epic
1
Already exists
Master epics should automatically inherit start and end dates from the release dates where the epics reside
With a master epic you can enter a start and end date, or have it be automatically calculated. The problem/idea is that this automatic calculation of start and end date should be based on the release dates for the releases in which the epics reside.
Guest
about 2 years ago
in Epic
0
Future consideration
When scorecards are applied to a product line, updates to the scorecard should not be applied to released epics. Since notifications for scorecard changes cannot be suppressed, changes to the scorecard result in a massive flood of email notificati...
Rachel Hiatt
about 2 years ago
in Epic
0
Future consideration
Currently, the user can link a feature to a master feature by searching by feature id. However, the user is unable to link a master deature by searching by master feature id. This creates an inconsistent user experience
Keith Davenport
over 4 years ago
in Epic
3
Future consideration