Remove Deleted Features from Database/Drop Down Menus
When you select a feature from drop down menu, even if previously deleted--it allows you add greyed out features. Why not archive them completely? It still allows for user to accidentally add the “deleted” greyed out item causing errors.
Guest
over 4 years ago
in Features
3
Already exists
On import, ask if you want to create duplicate record or replace by feature name. We can’t continue to add more features rows to your excel csv template if meeting with engineers and reupload…it doesn’t recognize duplicates and we have to start a ...
Guest
over 4 years ago
in Features
1
Future consideration
Status color key on top of feature board for those managers that don’t open details of each feature card
Status color key on top of feature board for those managers that don’t open details of each feature card. See print screen on how a color legend at the top of dashboard shows feature, debt, etc., color key on top of Tasktop Dashboard as an example...
Guest
over 4 years ago
in Features
0
Future consideration
When creating a custom field, we (1) select the Field Type and then (2) Name it. However there is no 'entry field' to store a "Field Descriptor" that would display on the Ideas Portal 'Ideas Entry Form' - instead of the name. So the workaround is,...
Kyle Crawford
over 4 years ago
in Ideas portal
0
Already exists
Ability to add context to to-do e-mail reminders - for ex: Initiative Name - to-do; Release Name - to-do
Aha! sends out the "consolidated" to-do notifications in e-mails which is a nice functionality. However, as the number of to-dos increase from various goals, initiatives, releases the confusion increases as to which context these are related to. F...
Our company has the Enterprise+ license. From discussing in you Online Chat, I've been told it is not possible to have different users on different pricing plans. When Ideas are submitted, it is the development team that come up with either the T-...
Guest
over 4 years ago
in Ideas
0
Unlikely to implement
Ability to add specific field from elements like feature (currently only defaults to feature name for example)
When adding other entities like scenarios to a feature, it is useful if we can associate a feature number rather than the feature name which is the default field when you use the many to many table
Arun Kalyanaraman
over 8 years ago
in Features
1
Already exists