Allow a field to be re-used across multiple sections of a dynamic ideas form
We currently use dynamic forms within our ideas portal. We've structured our forms such that we gather initial information and then direct the user to one of 6 branches, where specific information is captured relative to that branch. We would like...
Mark Eaves
over 2 years ago
in Ideas
0
Future consideration
The GANTT chart is currently the only roadmap-like display that is capable of displaying the rollup release properly. In high-level reviews with executives, when focused on features, the GANTT delivers exactly what is needed, BUT the phases can be...
Bastian Schoell
almost 3 years ago
in Releases
0
Future consideration
What is the challenge? Not able to move feature to next release What is the impact? Feature that have not been completed are shipped with the release Describe your idea When using a fixed workflow approval to ship a release, you should not be prev...
Stuart Blair
7 months ago
in Releases
1
Future consideration
What is the challenge? There are a number of views throughout Aha! where record cards are used to display information and can be filtered for multiple workspaces. The challenge is knowing which workspace each record belongs to without having works...
Jeanette Resnikoff
7 months ago
in Features
0
Future consideration
You can change the row background and the column header background for a pivot, but they both use the same value for the text colour. This means some combinations of the two backgrounds will not work together because the text will not be easily vi...
Jonathan Steel
about 1 year ago
in Roadmaps
0
Future consideration
Allow conversion of Epic to Feature when the Epic contains features
When an Epic has no child features, you can convert it to a Feature. When an Epic has child features, today you cannot convert it to Feature. It would be a smoother workflow to allow Epics with child features to be converted to a Feature
Emily Yankush
almost 2 years ago
in Epic
0
Future consideration
New User Story Map entered Epics should still require required fields and load the standard description field template
Problem: When adding entities (e.g., Epics) via the User Story Map, the user is not prompted to enter in required fields and the predefined Epic template is not loaded in the description field. This bypasses the Epic creation protocols elsewhere i...
Peter Bongiorno
almost 3 years ago
in User story map
0
Future consideration
As a product manager I would like to filter the portfolio view to eliminate goals, initiatives, and releases that are not yet scheduled or in development in order to show an uncluttered view to Executive Management for an entire productl ine.
Dan Molloy
almost 8 years ago
in Roadmaps
3
Future consideration
An easier way to reset "filters" in an existing view
What is the challenge? I've noticed that in certain views, a list report for example, if you change filters, etc. it enables the "save changes" button, but there really isn't a handy way to reset back to the current saved filters. What is the impa...
Guest
4 months ago
in Application
0
Future consideration
What is the challenge? UI designers spend time creating mockups from scratch. What is the impact? UI designers are already potentially using (or considering using) Aha! with their product teams so it would allow them to further use Aha! in support...
Scott Goldblatt
7 months ago
in Mockups
0
Future consideration