Epic
Sort by:
Recent
Status:
Future consideration
Showing 108
3
VOTE
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.
0
Future consideration
15
VOTE
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)....
1
Future consideration
2
VOTE
Dissociate Scorecards from Released Epics
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...
0
Future consideration
4
VOTE
Send notification for bulk updates
We had a situation where a colleague accidentally did a bulk update on our Epics moving them from one Initiative to another. We understand this happens. As a safety net, we would expect notifications to be sent to the watchers. This did not happen...
0
Future consideration
11
VOTE
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 ...
0
Future consideration
27
VOTE
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...
7
Future consideration
2
VOTE
Branch Logic - Conditional Formatting of Forms
We have sophisticated intake requests for portfolio work for which we use at the Epic level. To streamline this for our team we would like to have one form where a user is guided through conditionally displayed questions based on previous question...
1
Future consideration
9
VOTE
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 ...
1
Future consideration
1
VOTE
Allow dynamic links to be color coded (similar to tags)
Currently, tags in Aha have the format option to change the color. However the epic link, which appears the same as tags when created, does not. Most dynamic links are colored separately to indicate attached data, and it would be nice to have this...
0
Future consideration
4
VOTE
Add a standard Epic List under Feature menu
The current Feature menu doesn't provide an Epic List, and there is no way to see a list of Epics unless you create a custom list. It would be nice if you provide that as an option to include in the navigation to minimize having to create all thes...
1
Future consideration