What is the challenge? Named ranges require users to set ranges corresponding to time estimates. However, many teams use points as their common way of estimating. T-shirt sizes will correspond to a range of points. Points are also what come back a...
Max Robbins
10 months ago
in Capacity planning
0
Future consideration
Make viewing data in Aha! much easier and quicker, in less than 2 clicks
Users are really struggling with reports and roadmaps. They want to be able to find what they are looking for with just a couple of clicks and are overwhelmed with all the options presented to them under Roadmaps - as they have no idea what a pivo...
Deirdre Clarke
almost 2 years ago
in Reports
2
Future consideration
Require completion of certain fields with promoted ideas
Epic, feature and initiative layouts allow you to require certain inputs when these records are created in the platform. But if they are promoted from an ideas, portal, individuals are able to bypass the completion of these 'required' fields.
Danielle A
over 3 years ago
in Ideas
4
Future consideration
Show more context for added/removed records in retrospective report
I want to understand more about the records that are added to or removed from a release: When was it removed? Where was it moved to? What is its current status? I would like to see this information in the retrospective report
Jeff Tucker
over 1 year ago
in Reports
1
Future consideration
Intelligently reduce fields shown when adding fields to a report
What is the challenge? When I am building a report, every time I go to add a field to a report, I get a dropdown showing every possible field associated with that record. Fields for every custom workflow for every workflow in the account, tons of ...
Max Robbins
about 1 year ago
in Reports
2
Future consideration
Promoting an idea should copy the creator's information to the feature
What is the challenge? Currently, the "Created By" field on the idea card in Aha! displays only the name of the user who submitted the idea. However, this information is lost when the idea is promoted to a feature/epic, making it difficult to trac...
Guest
10 months ago
in Ideas
1
Future consideration
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...
Mark Gerrard
about 4 years ago
in Epics
8
Future consideration
Who would benefit? Solution managers, business leaders What impact would it make? Enrich OKR brainstorming sessions How should it work? We use an OKR canvas in an Aha! whiteboard to work objectives through to leading and lagging key results. Once ...
Chris Brooks
about 1 year ago
in Whiteboards
0
Future consideration
Allow a list report embedded in a dashboard to show more than 50 records
Currently list reports, regardless of length, truncate at 50 records when embedded into a dashboard. This makes it very difficult to use dashboards to manage large portfolios. There is also no message informing you of the truncation, so we did not...
Guest
over 1 year ago
in Reports
0
Future consideration
Capacity for teams currently allows you to create teams and add detailed estimates to records. However, we have a challenge with the way a team's capacity is calculated. We have cross-functional teams, which include people in product management, Q...