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 3 years ago
in Epic
7
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 option ...
Guest
about 5 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 5 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
over 3 years ago
in Epic
7
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
over 3 years ago
in Epic
2
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
almost 3 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 fea...
Julia Doyle
over 5 years ago
in Epic
1
Future consideration
Allow "Original Estimate and "Logged Effort" to be used in Calculated Columns
In Roadmaps list, having the ability to do calculated columns is incredibly powerful. However, we recently noticed that there are two fields we want to use to create charts that are not available to use. These are Original Estimate and Logged Effo...
Jared Gummig
about 3 years ago
in Epic
1
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 3 years ago
in Epic
0
Future consideration
Ability to sort epics on the gantt chart by something other than the four default options - specifically standard & custom fields
It would be beneficial to be able to sort the epics gantt chart by something other than the four default options. Specifically, a standard or custom field (and, ideally, also by the epic 'rank'). This will help: Ensure dates align with how things ...
Shannon Sauvé
almost 4 years ago
in Epic
1
Future consideration