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
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
What is the challenge? I need a high-level roadmap to summarize multiple workspaces, initiatives, and key milestones. Currently the gantt chart does not contain data at a higher level than the schedule, and the custom roadmaps do not allow me to i...
Who would benefit? All users What impact would it make? owner can customize the homepage they would like to highlight for team members. (for example: quick start guide note) How should it work? Owner can set default homepage for each workspace.
Ashton Tsou
10 months ago
in Account settings
1
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...
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
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
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
Allow features to be grouped by epic in feature board and feature workflow
Currently, there is no grouping available in feature board. In feature workflow, it is possible to group by assignee. It would be great to be able to group both views by epic.
Joao Tornovsky
over 3 years ago
in Features
0
Future consideration