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
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
SF - Aha Integration - Make Value Field Dynamic Based on SF Record
Right now, the vote section on an idea record via the SF integration only shows a value if it is an opportunity record. This is nice, but it ignores the evaluation of impact to existing clients value they may have which is tracked in subscription ...
Patrick Eslick
almost 4 years ago
in Voting
0
Future consideration
The key (IPLM-E-56) is worthless to external recipients and most business users. Instead, it reveals some inner workings (order it was created, how many, and some organizational info) that we don't want to share. So, I'd like to be able to hide th...
Guest
almost 4 years ago
in Roadmaps
1
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...
Allow items to be moved from one story map to another
It does not appear to be possible to move/copy Epics and Features from one Story Map to another. This is as essential as the ability to pick a post-it from one white board and stick it on another: at allows re-partitioning of the problem and exper...
Guest
almost 4 years ago
in User story map
0
Future consideration
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
Include Integrations reference filed in User Stories/Board Search criteria
This would benefit product managers that work in the Board view of user stories, with R&D teams using DevOps. Our teams use the DevOps user story ID in discussions and communications related to these work items. Currently, if I enter a valid D...
David Brown
almost 4 years ago
in Search
1
Future consideration