The first_name and last_name claims required by Aha! are not OIDC conformant, leading to duplicate information in previously conformant JWT tokens. This increases the size of tokens. This can also make it harder to use a common token for Aha! and ...
Guest
over 4 years ago
in User management
2
Unlikely to implement
Ability to apply a 'Release>Portfolio' filter and list of Releases to the 'Feature>Board' release views
Hi
Would be great if we had the option to take a saved filtered view from the 'Release>Portfolio' screen (therefore if you have created a view where only 3 of 7 active releases are visible) so that when you go to the 'Feature>Board' view onl...
Guest
almost 10 years ago
in Features
2
Unlikely to implement
We're starting to think there's too much functional goodness in Aha, that we could use less levels or fewer layers. Similar to how you can hide certain tabs of the the navigation, we think it could be useful to hide certain parts of the Aha data m...
Max Cascone
almost 8 years ago
in Application
4
Unlikely to implement
Add other key user groups like personas and competitors
It would be great if you could edit the persona name to something else if needed or to add another tab (like the persona or competitor) to track another business resource such as key suppliers.
Chris Waters
about 9 years ago
in Strategy
3
Unlikely to implement
Calendar Report: Colors and milestone (not release related)
Assign color to calendar items using specific criteria. This helps the audience understand the roadmap items relationships and possible impact.
Show events that are not aligned to a release. This helps for planning roadmap delivery and customer ...
Guest
over 7 years ago
in Reports
0
Unlikely to implement
Master Features and Features should be more interchangeable.
Aha wants to replicate the concept of epics as master features and features as stories. However, they treat them as separate entities which makes really hard to report a list of ‘features’ together (including master feature). For instance, JIRA ca...
Guest
over 7 years ago
in Features
0
Unlikely to implement
Allow the maximum votes per person per idea to be higher
Currently there is a 10 vote per idea cap. It would be nice to be able to allow a user to use all their available votes on one idea. This would allow the user to show that out of all the ideas, a single idea is the most important feature for them....
Guest
almost 7 years ago
in Voting
2
Unlikely to implement
Change which parking lot release the user story map creates records in
Currently the user story map creates records in the left-most parking lot release - the way we use our parking lot releases makes this not ideal and will require a process change. Instead, it would be nice if this was either user configurable to s...
Todd Meyer
over 5 years ago
in User story map
0
Unlikely to implement