We have a field that exists on both our Features and Requirements, and that custom field is being used in our JIRA integration. When creating a new requirement, it would be great to have the field auto-populate from what is specified in that field...
Guest
about 7 years ago
in Features
6
Future consideration
It would be great if, instead of just showing the underlying value, the scorecard metrics could use abstract labels... for example, for an 'effort' metric we might use t-shirt sizes such as "Small", "Medium", "Large" and "X-Large" behind the scene...
Guest
almost 9 years ago
in Features
6
Future consideration
Scorecard automated metric should allow you to select other scorecard fields
We have implemented two separate scorecards for feature cost and feature impact. This gives us more flexibility in reporting/filtering based on what-ifs. We would like to combine those two scores in an an overall feature score to use for prioritiz...
Rich Baldry
over 2 years ago
in Features
0
Future consideration
Have workflow status change dates refelect the most recent date a status was set
The value of “Status changed to <status X>” for a feature workflow appears to perpetually contain the date of the first time that the status was changes to <status X> rather than the date of the most recent transition to <status X&g...
David Kettinger
over 8 years ago
in Features
6
Future consideration
Prioritization Report - Allow more than one level of record structure
On the feature prioritization report, under the “edit columns” option, when I select “+ Add records related to this epic” it returns a blank list. I’d like to add initiatives to this list. This is needed when Epics are linked to Initiatives, but n...
Evan Hollohan
10 months ago
in Features
0
Future consideration
Rename product value field in non-product workspaces
The product value score terminology works well for workspaces where teams are building products. But in other workspaces it can be confusing. In these cases a more generic field name would be easier to understand.
Austin Merritt
over 2 years ago
in Features
1
Future consideration
In the old Aha! design there was an option on a feature to expand all the requirements. This was great for quickly showing all the links to Jira. Could you bring this option back?
Kelly Sebes
about 4 years ago
in Features
0
Future consideration
Allow Drill-in for Feature columns on Prioritization view
Who would benefit? Users sharing Prioritization views via shared webpage What impact would it make? Increase ease of use for drill-in functionality by enabling the function on the default columns How should it work? The default Feature Name column...
Stephanie Lechner
about 1 year ago
in Features
0
Future consideration
Teams can inherit delivery risk settings from the team line.
One can set delivery risk settings on the team line but these appear to have no effect. It would be nice to have teams be able to set their delivery risk settings to inherit from their team line, similar to how card customizations are intended to ...
Paul C
over 1 year ago
in Features
0
Future consideration