Please Break Out Epics from Features in My Work View
Currently, Features and Epics are grouped together in the My Work view under features. This is not clearly intuitive and it would be great to see them separately.
Guest
almost 2 years ago
in My work
0
Future consideration
Option to remove Archived Goals / Initiatives from report filters
I use the Hierarchy report regularly to review the overall picture on Goals and related Epics. When working with other departments I like to reduce the noise in this report to filter down to their items only. However as it includes archived items,...
Guest
over 3 years ago
in Strategy
0
Future consideration
Within a given product there can be different types of initiatives and features. Aha! supports the concept of feature types and allows templating of the description field by type. Would like to see an expansion of this concept to support configura...
Bonnie Trei
about 5 years ago
in Features
5
Future consideration
Without having to assign someone as a workspace owner, please add a "notify user" field that will pull from the list of valid users for the person submitting the request to pull from. This field should allow for multiple users to be chosen to rece...
As a viewer/advisor to a product lifecycle, I will never own and seldom create any records (meaning that "My Work" is empty!). Therefore, the only way to track a record (idea/epic/anything) is to add myself as a watcher. First, doing this is sligh...
Guest
over 4 years ago
in Application
5
Future consideration
Allow for changing column width of Custom Table views
When custom tables are viewed, the column widths is defaulted by the system and doesn't allow for customization. For better usability, it would be great if we can change the display width of the columns
Karla Johnson
over 3 years ago
in Reports
1
Future consideration
When setting up an integration, it would be helpful to have a way to be prompted to map required fields in Jira. Currently, it is possible to create an integration that does not have field mappings for required fields in Jira. This causes the inte...
Madeleine Black
about 2 years ago
in Jira
1
Future consideration
Do not allow requirements to be mapped without a Links To relationship set
It is possible to create an integration where you have requirements mapped to a Jira record type, and where you have no Links To relationship established to a parent record in Aha! This results in import errors where requirements cannot be importe...
Madeleine Black
about 2 years ago
in Jira
0
Future consideration
Add Jira "Project" and "Board" fields to integration reports
There are quite a few fields in the 'Integration" schema, but two very useful fields in the JIRA integration are missing. If we could get at least "Project" added to the list of fields, it would allow us to tell which workspaces are integrated wit...
Alan Thorpe
over 3 years ago
in
4
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