All ideas
Sort by:
Trending
Filter by:
Status
Showing 8941 of 8941
4
VOTE
Allow me to open release drawer from release retrospective report
Who would benefit? All customers using the release retrospective report What impact would it make? It would allow me to easily drill into the release for additional context when questions are coming up in review of the report How should it work? T...
0
Future consideration
4
VOTE
Limited layout functionality on capacity team record
Who would benefit? Users who would like to add custom fields to the account settings > capacity planning > teams view What impact would it make? Ability to add custom tabs and add rows to a custom table How should it work? When editing the l...
0
Future consideration
21
VOTE
Allow feature boards to show releases and their features across multiple products
This would allow for an easy view that can be used to review and prioritize features, especially when features across multiple products have dependencies. Viewing and filtering multiple releases from different products in the same features board w...
2
Future consideration
4
VOTE
Search Note record type edit history
Who would benefit? All teams that use notes What impact would it make? Easily find correct past versions in edit history How should it work? Search bar within edit history in Note record types to pinpoint where in the history something changed (ba...
0
Future consideration
10
VOTE
Allow nesting of rollup releases
Rollup releases are very useful in organizations with complex and nested product lines and products. A top level product may have a V2.0 which is a rollup of three subsystems, a perfect use case of a rollup release. If each of the subsystems, in t...
3
Future consideration
3
VOTE
Support mapping Asset object fields through Jira integration
Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...
0
Future consideration
6
VOTE
Allow detailed estimates to affect capacity plans without needing to assign a team member to the Aha record
We do all of our assigning in Jira, and in fact only sync epics between Aha and Jira, so adding an assignee in Aha doesn't make sense for us as you don't assign a dev to an epic, even in Jira. We assign to the task/sub-task. Having to add an assig...
0
Future consideration
13
VOTE
31
VOTE
1
VOTE
Kanban - Workflow Heat Map
What is the challenge? When running an effective Kanban system it's important to know where the bottlenecks in the process are. What is the impact? Currently I have to export the data to a spreadsheet to work out the problem stages. Describe your ...
0
Future consideration