Option to not copy Requirements when Copying a Feature
What is the challenge? We have begun tracking high-level Requirement information in Aha! and have seen that when we copy a feature the stories are also copied. This may be appropriate in some cases, but not all. What is the impact? This may create...
Lorena Connolly
over 1 year ago
in Features
3
Future consideration
Drag and drop is onerous only available in full release view. User should be able to directly enter rank position (or even before/after another ticket reference.)
Guest
over 9 years ago
in Features
13
Likely to implement
I would like to be able to include the value from another scorecard in a scorecard.
We have some attributes in our total score calculation that indicate how valuable this would be for customers and another that indicates the value for prospects (a...
Alex Horan
over 8 years ago
in Features
1
Unlikely to implement
Showing running total of capacity field in prioritization view.
What is the challenge? PM can't easily tell which items are beyond the current remaining capacity. What is the impact? Currently, only board view can shows limit line. However, many users use prioritization view to prioritize records based on capa...
Ashton Tsou
over 1 year ago
in Features
1
Future consideration
Feature Date Range Calculation Method Not Exposed for Reporting
What is the challenge?
The referenced field is not available for reporting. While there is a default for this setting, it can be overridden on an individual feature basis.
What is the impact?
The only way to tell how it is set is to manual...
Mike Unum
about 2 months ago
in Features
0
Future consideration
Improve the way that AI embedded prototypes can be moved around a record description
What is the challenge?
Currently, you can create an AI prototype and add this to a record's description. The AI prototype is difficult to move around the record description if you need to reorder where it exists in context of other content in th...
Terence Osmeña
4 months ago
in Features / Notes
0
Future consideration
What is the challenge?
From a tool maintenance perspective, we have to individually maintain drop down values for similar fields. This presents problems with allowing for standard integration paths when different groups have their own field like...
Guest
6 months ago
in Features
0
Future consideration
Sync status updates between Features and their associated Releases
Currently when any feature changed their status from Backlog to In Progress, the associated Release should be manually updated to reflect the changes. There is a functionality to sync status updates between epics and their associated features, and...
Guest
over 4 years ago
in Features
2
Future consideration
Bulk update "Location" for Features and Requirements
What is the challenge?
Currently, when features or requirements move between different stages (e.g., from Backlog Management to Prioritized Backlog), the "Location" field must be updated manually for each individual item. This is time-consuming ...
Jeff B
4 months ago
in Backlogs / Features
0
Future consideration
Similar to Capacity line in the feature board , we would like a target, commit, and stretch line with user defined % of capacity. Ex, 80% = commit, 100% = Target, 120% = Stretch with 3 lines. This way I could have a quick visual of my capacity in ...
Guest
almost 10 years ago
in Features
1
Future consideration