Here's what I think would be ideal for scorecards, using a RICE model: Allow the user to select a text value that corresponds to the numeric score. This will help consistency across users and projects. So that a score for "Reach" might be expresse...
Bjorn Aannestad
almost 3 years ago
in Features
3
Future consideration
Capacity Report - pulling time from differing fields
We need the ability for the report to pull the estimate from a feature AND if there are multiple time estmates on the requirements tab , the aggregate of that time needs to overwrite the time range on the overview tab on the feature
Master Feature release should be automatically established from Feature release info (i.e. inherit the last of the due dates of the features)
It is extremely inconvenient and the cause of much manual reconciliation that the Master Feature release (and date) isn't *automatically* established as the latest of the related Feature releases (and dates).
So can the Master Feature release rele...
Mark D
over 7 years ago
in Features
1
Unlikely to implement
Update status of requirements on status change of feature
I don't want to change the status of each and every requirement individually when changing the status of a feature. For example, when I hand off a feature - which has 5 requirements, for example - to engineering to spike, they come back with a ful...
Guest
over 9 years ago
in Features
4
Unlikely to implement
Quick way to reference existing Personas within Features and Requirements.
As a product manager, every day I am creating a new initiative (less often), feature and requirement. In the writing of User Stories, whether it's a feature or a requirement in Aha!, best practice is to mention the person for which the feature wil...
Matt Wagnon
over 7 years ago
in Features
3
Unlikely to implement
Move attachments (mockups) from feature to requirement
In the process of defining features, I create mockups and attach other files supporting the feature. Later, I'll break down the feature into product backlog items and I use requirements for that. It would be so awesome if there was a way to move a...
Tom Beck
over 6 years ago
in Features
2
Future consideration
Ability to choose fields to show on parent record when customizing card layouts
Who would benefit? Any users who have customized card layouts and want to display consistent information. What impact would it make? Consistent visualization across all card types; elimination of distracting fields. How should it work? Today, when...
Kim Bremer
12 months ago
in Features
0
Future consideration
When a feature has a record link created to it that ties it to another feature, there is the Record Links section which shows the dependencies (depends on, contains, etc.)
Well, it doesn't appear that we can see who has linked what records to what...
Guest
over 7 years ago
in Features
1
Will not implement
The feature board shows a column for each release, but unless you name the releases to be identifiable (I use release versions), then it's hard to quickly see the theme of each release. It would be good to have the option of displaying the release...
Kristian Kauper
over 9 years ago
in Features
0
Unlikely to implement
When visualizing record links be able to customize the view to show aha reference numbers, release name, etc.
If you have a master feature you can’t easily link from the master feature to an existing feature. This really, really should be fixed and is probably the preferred way since you can already create a new feature in any product from a master featur...
Gavin Saldanha
over 7 years ago
in Features
0
Already exists