Alert when moving a feature from one product to another
We love Aha! for it's flexibility. However, it would be great to configure something platform wide (our platform). We would love to be able to have warnings if the user tries to move a feature from one product to another. This happens to us (accid...
Guest
over 9 years ago
in Features
1
Will not implement
Stop showing empty releases when I use the filter by release owner on the feature board
I use the feature board all the time. We have a product that has many releases and they are owned by different product owners. So I use the filter "filter by release owner" so that only my releases show up on the board so I can do all my managemen...
Guest
over 8 years ago
in Features
0
Future consideration
Similar to the ability to create Ideas via email, we would love the ability to create Features via email submission. Our ideal workflow is to have support issues and bugs submitted into Aha! and this would simplify things so that users aren't send...
Danette Colin
over 7 years ago
in Features
0
Will not implement
When using a scorecard, given the way users think about scoring, rather than using a numeric scale, I would like to be able to assign text [as the slider element] and have this equate to set values
As an example
Technical Feasbility would have 3 v...
Mark Brown
over 6 years ago
in Features
2
Future consideration
Coalesce common dependencies in the dependency map
Right now, I have a task which depends on several other tasks, and some ofthose depend on the same underlying tasks. An example of this would looklike:
A / | \B | C \ | / D
I would expect the dependency map view to draw a line between B&D as ...
Do not count "will not implement" requirements in feature effort estimate
What is the challenge? If a requirement is listed as "will not implement" the detailed estimate is still counted in the feature effort calculation What is the impact? Currently need to manually adjust requirements to 0, in ADO if we mark the user ...
Guest
8 months ago
in Features
0
Future consideration
I would like to be able to organize custom fields by moving them to other "tabs" on Feature tickets.
What is the challenge? I have too many custom fields on one page when opening a Feature What is the impact? It takes me too long to scroll through the Feature to find the field I need Describe your idea I need to be able to organize custom fields ...
Our Use Case
We have a process that we've actually implemented as a product within Aha! that helps us track Change Requests. We set it up as a separate product within Aha! because this process has a different workflow that we wanted to capture, in...
Sikia Soller
almost 7 years ago
in Features
0
Future consideration
When using Aha! Develop to track bugs I want to see specific fields that are only relevant for a Bug record. EX. Severity, date raised, reproduction steps etc. So that I can report on this specific subset of record types and their progress without...
Ian Cooper
over 2 years ago
in Backlogs / Features
0
Likely to implement