PINNED
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...
Improve mapping capabilities for "Idea category" custom field.
What is the challenge?
You can add a custom field on epics, features, etc. for "Idea categories". When an idea is promoted, the idea's category will be copied to the epic or feature automatically.
This can be mapped one-way from Aha! to Jira to ...
Emily Yankush
5 months ago
in Ideas
0
Future consideration
The current Aha! Kanban board does not provide the flexibility other tools such as SwiftKanban provide. Is there any plan to build an integration into Swift Kanban and/or is there any plan to build out a more robust kanban board within Aha! We hav...
Guest
over 6 years ago
in Application
5
Unlikely to implement
What is the challenge?
Currently, only the "parent" Roll-Up Release's Name, Internal and External Release Dates map to "children" Sub-Releases.
What is the impact?
Once Sub-Releases are added, user has to manually update their Status, Rele...
Carrie Garrett
5 months ago
in Releases
0
Future consideration
What is the challenge?
Users don’t receive any notifications when their comments are Liked. This makes Likes essentially invisible to the comment author, reducing their usefulness as a signal of agreement or engagement.
What is the impact?
...
Teresa Bever
5 months ago
in Ideas
0
Future consideration
AI Assistant: Define AI agents, prompts and instructions in a workspace template
What is the challenge?
Rolling out account-wide AI agents, prompts and instructions across many workspaces is time-consuming
What is the impact?
Administrators can't easily assign new AI agents, prompts and instructions to many workspaces ...
Dale Potter
5 months ago
in AI assistant
0
Future consideration
What is the challenge? There are teams who only use Epics in their workspaces, but the date range of Releases can only be calculated from Features. Moreover, there are no automation rules or integration mapping options to automatically update the ...
Hank Liu
over 1 year ago
in Releases
3
Future consideration
What is the challenge? Currently, Aha!’s automation only supports conditions on the trigger—not on the actions. This creates a need to duplicate automations for each variation, such as routing Epics to different Jira projects based on the assigned...
Robert Rodriguez
8 months ago
in Automations
0
Future consideration
Hide will not implement / shipped releases in Releases -> Gantt View
What is the challenge? I have no easy way to hide will not implement releases from the Gantt View Other views automatically hide these releases by default. What is the impact? Confusion & Time: If the release is 'will not implement' then I lik...
Cheryl Hatos
over 1 year ago
in Releases
0
Future consideration
Allow custom due date options for to-do automation actions
Who would benefit? Users who are looking to automate the creation of to-dos, approvals or work requests What impact would it make? Allow more flexibility in to-do creation How should it work? Similar to how we can select the custom date option whe...
Kristina Gass
about 2 years ago
in Automations
4
Future consideration
Add aggregated series support to pivots and charts
What is the challenge? We've recently added 'time in status' functionality to our reporting system. It would be useful to be able to visualize something like: "average amount of time features have spent in a given status by workspace." it could ma...
Chris Zempel
about 1 year ago
in Reports
2
Future consideration