All ideas
Sort by:
Trending
Status:
Showing 9109
2
VOTE
Show feature status change in epic history
Who would benefit? All users utilizing epics, features, and workflow syncing What impact would it make? How should it work? Currently when a feature status change causes an epic's status to change due to workflow syncing, the epic history does not...
0
Future consideration
3
VOTE
Return raw value changes in /api/v1/audits
What it looks now: { "audits": [ { "changes": [ { "field_name": "Assigned to user", "value": "Default assignee → Anton Aha", } ] } ]} Proposal: { "audits": [ { "changes": [ { "field_name": "Assigned to user", "value": "Default assignee &a...
0
Unlikely to implement
3
VOTE
17
VOTE
Capture and Track User Testing Feedback
While I understand there are work-arounds for capturing user testing feedback (https://big.ideas.aha.io/ideas/APP-I-464) the work-around does not effectively enable a wider set of end-user testers to quickly provide feedback results.
It would cer...
2
Unlikely to implement
9
VOTE
Reference Fields for Capacity Estimates Costs, Teams & Team Hours
We'd like to be able to pull information from the capacity planner fields: team name, team hours & cost per team. There is already some kind of way to do this within the pivot table that comes with the capacity planner; however, we'd like to s...
0
Future consideration
3
VOTE
Feature linked to multiple epics
Create ability for a feature to support multiple epics across workspaces. This will allow a single team that's working on a single feature that supports multiple epics across multiple teams. Currently we have multiple teams enabling a feature and ...
5
Unlikely to implement
9
VOTE
13
VOTE
Support mapping tags to JIRA multicheckboxes
Problem Overview It is possible to bi-directionally map tags in Aha! with custom multicheckboxes in Jira. However, it is not possible to configure how the values should map on each side. This creates errors when the two fields attempt to sync. Pro...
0
Future consideration
2
VOTE
Display named range value on Overview tab "Initial estimate" field
Who would benefit? Teams using capacity planning for teams, planning with named ranges (e.g. t-shirt sizes) What impact would it make? Currently, the "Initial estimate" field includes the resulting time-based estimate, but not the range I've selec...
0
Future consideration
2
VOTE
Embed notes in record description (same appearance as whiteboards)
Who would benefit? Product teams build up documentation relevant to specific epics and features. You can currently add this document to the Research tab or add it as a link in a record description, but this does not give a user a preview of what t...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved