As you create more and more strategy models, it would be useful to have a way to organize models into a hierarchy (like you can do with Notes) and/or into folders. You can currently filter the models based on type or time frame but that doesn't pr...
Greg Horlacher
over 4 years ago
in Strategy
0
Future consideration
When assigning To-Dos to someone, it'd be useful to know how much time they're spending on it, rather than just Done/Not Done. That could be rolled into the feature/requirement/etc's time estimates, too.
This would need to be enterable by Reviewers.
Max Cascone
over 7 years ago
in To-dos
0
Unlikely to implement
I understand that Features are not to be touched by Reviewers, but User Stories are items that typically get assigned to non-product managers. It would be extremely useful to allow Reviewers to log time on Requirements, so the Product Manager can ...
Max Cascone
over 7 years ago
in Features
1
Unlikely to implement
I would like to be able to promote ideas to goals and not just epic, features or initiatives. We use ideas to gather all request from our stakeholders and sometimes the idea is bigger then a i.e. features and we need to plan it in togheter with al...
Dagny Lydsdottir
about 3 years ago
in Ideas
0
Future consideration
Limit contributors or another role to edit selective fields
Contributors or another role should have the capability to edit selective fields (ie Internal Notes or Description) vs all fields like the product owner. By default, the field should be editable by the product owner, but there should be a setting ...
Christina Wongbuphanimitr
over 7 years ago
in Features
1
Unlikely to implement
It would be great to allow for cards (epics, features, requirements) to move in any "card" based view. A great example is Google Keep (Web version on Desktop). Google Keep allows for easy moving of cards and pinning of favorites to the top. Add in...
Todd Materazzi
over 1 year ago
in Features
0
Future consideration
better validation warnings and units tips and handling on estimates fields
the toolips on estimates fields need consistent messaging in all field contexts, with proper messaging/tip content based on the units of the configuration. this needs to be the UX when creating (actual configured units not a hard-coded either/or t...
Kevin Martin
over 1 year ago
in Capacity planning
0
Future consideration
please let admin better control the field choices on apply rank to users cannot make bad choice
apply rank opens a picker to let user decide which custom field to apply the rank value to , and that custom field needs to be the field in the mappings that provide update into target tooling (my case, its ADO, stack rank). I see multiple custom ...
Kevin Martin
over 1 year ago
in Roadmaps
0
Future consideration
Allow using automation to change the parking lot of new features in Aha Develop
When creating automation for features in Aha Develop, it's not possible to change the parking lot (workspace) of the feature. There is a variety of fields that can be changed, but unfortunately, the parking lots are not among them. This would help...
Niklas Gromann
over 1 year ago
in Features
0
Future consideration
It would be good to be able to visualise the data model in a knowledge map or hierarchy map view for the respective Workspace. e.g. how Goals, Initiatives, Master Features and Features are connected. Not all audience wants to see Roadmap view with...
Guest
about 3 years ago
in Reports
1
Future consideration