What is the challenge? The custom types configured in the features status/workflow configuration display with the field name "Type" on the feature layouts. The "Type" term cannot be customized. What is the impact? The term "Type" doesn't align wit...
Enable custom feature types to apply other records
What is the challenge? The custom types (configured in the features status/workflow) are only available for features. This type categorization is needed for other record types, including epics. What is the impact? The current workaround is to use ...
What is the challenge? There is no easy way to send ideas to engineering to work on or keep the information in sync. What is the impact? Time spent copy and pasting data. Out-of-date information leading to confusion. Describe your idea Like the re...
We need the ability to export the email address associated with a user into a reportable format.
What is the challenge? Currently we are unable to see the email address associated with a "user" in the front end of Aha. This is breaking an automation our finance team currently uses the email address for. We have several users with the same nam...
Jeff Krueger
about 2 months ago
in Reports
0
Planning to implement
Calculate initial estimate from estimates on child Features
What is the challenge? Initial estimate for large capabilities (Epics) does not calculate based on estimates of child Features What is the impact? Confusion by engineering on the level of confidence expected for roadmap-level estimates Manually ad...
Have todo custom fields be a part of release templates
What is the challenge? Same as this idea, but for todos - https://big.ideas.aha.io/ideas/A-I-16116 There is now support for custom fields on todos, but these cannot be set within a release phase template. For teams using Aha! for project managemen...
Max Robbins
about 1 month ago
in Releases
0
Future consideration
Sort the list of release templates to appear in alphabetical order or set manually
What is the challenge? Large lists of release templates can be difficult to manage and sort. Not having a set list and being able to sort the order alphabetically or manually increases the time it takes to find a release template. This is also the...
Terence Osmeña
4 months ago
in Account settings
0
Future consideration
I have certain fields that need to be filled in before moving to the next status in my workflow. The data for these fields is not known in the previous statuses, so it can't be set as a required field before the record reaches a certain status. Th...
Bonnie Trei
about 4 years ago
in Features
13
Future consideration
Instead of listing features within the same epic in alphabetical order, it would be helpful to be able to rank features within epics, not only releases.
Amanda Chan
almost 3 years ago
in Epic
7
Future consideration
What is the challenge? People don't keep their roadmaps data complete and up-to-date What is the impact? Consumers of the roadmap don't have the information needed when interacting with the roadmap and either make incorrect judgments based on that...
Guest
9 days ago
in Roadmaps
0
Future consideration