Support work item types (think feature templates) as defined within the Kanban community
Support work item types as defined within the Kanban community. Possible solution: Extend Aha!'s existing custom type to include a pre-defined list of requirements or to-dos. Add the ability to apply the new custom type to existing features and wh...
Brad Black
almost 4 years ago
in Features
0
Future consideration
Idea bubble chart's Color dimension needs to be fully customizable
We need the ability to control the Idea bubble chart's Color dimension's gradient scale and numeric range/scale, just as we can control all aspects of the other dimensions in that bubble chart.
Currently, the Color dimension applies a seemingly r...
Every status in the Idea portal may have a color and colors are very suitable to distinguish them visually without long reading. At the moment, when we try to filter Ideas, on the user portal, by their statuses we see their name with a highlight. ...
Guest
almost 4 years ago
in Ideas portal
0
Future consideration
At the moment a single accessible login option is an Email. At account creation it is required to provide information like name and in case of need user can upload an avatar. At the same time a lot of people already have their Social media account...
Guest
almost 4 years ago
in Ideas portal
0
Future consideration
A way to account for Engineering teams not aligned to Products
We have a a large and complex code base that requires our Engineering teams to be aligned with components, rather than products. With multiple products using multiple engineering resources, it makes release planning just short of a nightmare. Havi...
Support iovation LaunchKey for Multi-Factor Authentication
Currently you seem to only support stronger authentication options for those customers who use Duo (under their own contract). While we would be OK with an Aha! contracted strong authenticator, if we must supply our own then our preference would b...
Guest
over 7 years ago
in Integrations
0
Unlikely to implement
Pivotal Stories added to Epics converted to Requirements in Features
The Pivotal integration is good, but fails to capture a common case for us. Our teams often add new Stories to Epics that are essentially Requirements on the corresponding Feature. We track progress through these Stories/Requirements. Right now, t...
Christopher M
almost 4 years ago
in Pivotal Tracker
0
Future consideration
Sub Visibility Roles. Challenge: Allow colleagues to comment/view the notes area only, but not have visibility in other areas of the workspace Solution : Visibility rights per role level, similar to top bar customization per workspace (pen)
No description provided
Guest
almost 4 years ago
in User management
0
Future consideration