Epic
Sort by:
Trending
Filter by:
Status
Showing 120 of 7169
5
VOTE
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...
1
Future consideration
8
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)....
0
Future consideration
9
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...
2
Future consideration
1
VOTE
2
VOTE
9
VOTE
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.
2
Future consideration
7
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 ...
0
Future consideration
2
VOTE
Epics as collections of Features (or Ideas) without being tied to a release.
We use Features as user stories that get individually worked within a release (development iteration). However, almost all of our Features roll up to Epics (which then roll up to Initiatives). The current format doesn't allow for the organization ...
0
Future consideration
14
VOTE
Prioritize master features within initiative
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 ...
0
Future consideration
3
VOTE
"related" features/activities have details
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...
0
Future consideration