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
over 3 years ago
in Features
0
Future consideration
Need the ability to adjust the size of the drawer to show more tabs
Given that all custom tables are now shows as tabs, the drawer shows at most 4 or 5 tabs depending on the resolution. However, while working on that, it would be very efficient if the size of the drawer can be adjusted by user so we can drag and m...
Arun Kalyanaraman
over 3 years ago
in Application
0
Future consideration
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
over 3 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
over 3 years ago
in Ideas portal
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
over 3 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
over 3 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
over 3 years ago
in Roadmaps
1
Future consideration
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
over 3 years ago
in User story map
0
Future consideration
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
over 3 years ago
in Search
1
Future consideration