There is no way to set the # of Ideas/Features/etc you can see. If you want a list of 25 or 50 or see All. Seeing ALL would be beneficial. It would be great to have expanded features around Pagination.
Jason Soffer
over 5 years ago
in Reports
1
Future consideration
There can be a lot of stuff listed under steps. Freeze (or lock) the row of steps so that as you scroll down to see the items below, you don't lose sight of what the steps are.
Tom Beck
over 5 years ago
in User story map
1
Unlikely to implement
Limit previous months visibility on Capacity Planning - Set Advanced Estimate Screen by time
I would like to limit the number of visible months in the Capacity Planning Detail view for any of my initiatives. See source issue: https://support.aha.io/hc/en-us/requests/499309
Mike Jacobson
over 4 years ago
in Capacity planning
0
Future consideration
We move customers from opportunity into lead generally before we can capture their ideas. They are then leads for their lifetime with our business. With the current Aha! Salesforce integration, we can't capture their ideas through Salesforce.
Melih Onvural
almost 9 years ago
in Salesforce
3
Future consideration
Engineering managers & team leads sit "in between" Aha! Roadmaps and Aha! Develop. They more than just team owner permissions, but not full workspace contributor permissions. Key use cases Team leads can provide initial estimates on features b...
The Release Portfolio is a good start on providing the ability to visually schedule resources, but it lacks some simple and extremely useful features:
Simple leveling. There should be a way to assign resources to each feature, and level the sched...
Kristian Kauper
almost 10 years ago
in Releases
2
Already exists
I want to rerank features in a release by master feature rank.
When pre-planning a release, I want to be able to move sets of features around under master features to ensure that there's enough capacity in a release to complete the full set of features under a master feature. To do this I want to rank all the...
Mat Jennings
about 7 years ago
in Features
3
Unlikely to implement
What is the challenge? Currently there is no automated way to visualize the tracked risks for reporting purposes (e.g. classical risk matrix) What is the impact? The user has to use multiple tools for reporting, instead of using Aha! as single sou...
Guest
7 months ago
in Reports
0
Future consideration
What is the challenge? A Slack Messages used to add comments to aha records or create ideas, by default, does not have context around who sent the message, when, what slack channel What is the impact? Either the context around the message is lost,...
Michael Gogos
7 months ago
in Slack
0
Future consideration
Component lookup by numeric id for relationships, hashtag referencing etc
Currently, when looking for a specific component via relationship or when using "#" in a note/comment etc and you know the id, you always have to put in the whole id including the workspace prefix. If you only use the numeric id, you don't see any...
Guest
almost 3 years ago
in Search
0
Future consideration