Now/Next/Later Roadmap - Configure columns based on Status field
Who would benefit? Product Teams who actually follow the Lean Roadmapping approach. Please read this awesome overview from Janna Bastow: https://www.prodpad.com/blog/invented-now-next-later-roadmap/ What impact would it make? "The Now-Next-Later r...
Stephanie Redl
almost 2 years ago
in Roadmaps
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
about 4 years ago
in Ideas
4
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
almost 5 years ago
in Epics
9
Future consideration
Hi,
I'm looking to have the ability to change different behaviors based on field values.
For example, let’s say I added a custom field called “expected feature date”, and I assigned this feature to a release, where the release date is larger than ...
Noam Green
over 7 years ago
in Features
1
Future consideration
Ability to do subtotals in Pivot tables (in addition to Grand Total as it is today)
For ex: if we have a dollar value (numeric custom field) associated with each release, let's say it's the release cost - I would like to be able to add up all release costs per each product (sub-totals) in the same product line, in addition to the...
Guest
about 8 years ago
in Reports
5
Future consideration
Consistent Matrix\Chart behavior and add to features
The Matrix\Chart view for Initiatives and Goals should have the same behavior as Competitors and Ideas when the axis can be changed to represent different values of a scorecard.
Features should have a Matrix view based on score cards
Ryan Thiessen
about 10 years ago
in Features
7
Future consideration
Provide the ability to customize what is sent within automation emails
We use automation emails to notify PMs and a few others anytime a new idea is posted. These contain no information beyond the name of the idea and a link. As an Aha admin, I want the ability to select the specific fields I want to include in autom...
Brian Trombley
over 5 years ago
in Automations
9
Future consideration
Integrations 2.0: Add dependency link to connect records without natural relationships together
In integrations 1.0 if I mapped Features = Story Requirement = Task Aha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other. ...
Danny Archer
about 8 years ago
in Dependencies / Jira
3
Future consideration
Capacity for teams: Update time-based estimate as record timeframe changes
Setting people estimates and then visualizing a report by people per month is a key capability in estimating team capacity and the ability to execute on a roadmap. When capacity for a team is exceeded, there are usually two recourses: Assign the i...
Gianmarco Spiga
over 4 years ago
in Application
3
Future consideration
Currently, if you need to use a custom roadmap and the "show text inside thick line" option, text doesn't wrap. So if you need to display a good amount of text - a feature or master name, tags or labels, short summaries etc - you just get this ext...
Guest
over 6 years ago
in Roadmaps
6
Future consideration