Once a capacity plan has been built, it would make it easier to do what-if type comparisons if you could create a copy of a Scenario pre-populated with the estimates already in the initial scenario. This would let you change aspects of the capacit...
Mike Wachal
over 2 years ago
in Capacity planning
0
Future consideration
We want to view our releases in a Kanban-style workflow, in the same way that we can for Initiatives, Epics and Features. This would support the way we work and streamline it across all levels of the hierarchy.
Marcie Gardner
over 2 years ago
in Releases
0
Future consideration
In a report, I could use the ability to filter ideas based on whether they have comments or not. For example, "Public Comments Count > 0". This would be more useful than sorting by the comments count field, as it would return a much shorter rep...
Matthew Ryan
about 4 years ago
in Reports
1
Future consideration
when copying features also copy comments associated with that feature
would be helpful for most users.....seems like it would be a simple tweak since you are able to copy comments today...but the comments don't copy over.
Guest
over 7 years ago
in Features
2
Will not implement
I want a user-impersonate option to let me and your staff debug user experiences
I want to login as a user with less rights (ie a simple contributor or reviewer) who has reported unusual behaviors I do not see myself. For example, I want to open incognito, go to an admin account feature, login as "impersonation" of a user I pi...
Kevin Martin
over 1 year ago
in Account settings
0
Future consideration
Currently, Aha allows users to add milestones to features using the Gantt Chart view (example). These milestones can be useful for communicating intermediate value delivered to leaders outside of features, which may extend to 3 months or more in d...
Marcie Gardner
over 2 years ago
in Reports
1
Future consideration
we frequently see the need to uplevel a story with many requirements to an initiative level with many stories. Having this functionality would allow us to do this easily
This usually happens when we start to groom a feature and realize it should b...
Guest
over 9 years ago
in Features
1
Already exists
There needs to be improvements to the Reporting navigation. Informational viewers get lost in the Aha! UI for reporting. If you are a viewer, you should have a simple UI experience. For me, it should be directed UI experience.
Guest
almost 7 years ago
in Reports
2
Future consideration
I'd love the ability to lock a release's start and finish date, and its children features have to stay within those dates. If they don't provide some kind of feedback or alert that the feature has strayed out of its bounds.
Also, in the Releases...
Max Cascone
over 7 years ago
in Releases
0
Unlikely to implement
We would like to be able to 'lock down' some fields unless there is approval to change them. For example, Release date (or due date) Budget Designated people in the company would be required to approve any changes to these fields. Along with this,...
Kelly Sebes
about 5 years ago
in Releases
1
Future consideration