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 2 years ago
in Epic
4
Future consideration
In complex software development we often have features that require the coordination of changes across multiple software products. In these cases we create an Epic to represent the overall capability we wish to deliver, and place related features ...
Andrew Foster
2 months ago
in Epic
2
Future consideration
Include Milestones in the expanded Release names section of the Epics Gantt Chart
Many companies use milestones to represent when a set of work items is to be delivered and these are only loosely coupled or decoupled from longer-term planning time boxes, which in Aha are best represented by Releases (e.g. quarterly time boxes)....
Rich Stewart
almost 2 years ago
in Epic
0
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 3 years ago
in Epic
0
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 2 years ago
in Epic
2
Future consideration
Sometimes I just need to review my list of Epics, and get there with a quick click and without needing to go through the Stories list, showing the Epic, sorting on that column. I want an 'Epics List' view as a base start of a report/view.
Gwen St. Pierre
10 months ago
in Epic
1
Future consideration
As part of our strategic planning process, we want to prioritize all Master Features (irrespective of product line/product) in our entire portfolio. Right now, there's no way drive prioritization at this level.
We need to stack rank and prioritiz...
Kirstin Maurer
over 4 years ago
in Epic
2
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 4 years ago
in Epic
6
Future consideration
Assign an epic to two initiatives. We can have a piece of work, e.g. update master data, that can contribute to more than 1 initiative. I tested it out and if you add an epic from another initiative, it moves it rather than adds it
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 4 years ago
in Epic
1
Future consideration