PINNED
Chrome extension to capture feedback from anywhere [Shipped!]
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...
Elle reads external sources for context (e.g. Skills Shared Repositories or Product Documentation)
What is the challenge? Elle can´t read automatically data repositories outside Aha! for example Skills in shared repository in GitHub or Product Descriptions documents in SharePoint, or Confluence pages.
What is the impact? When asking for creati...
Add support for aggregate logic in automations (e.g., parent status based on all child record statuses)
What is the challenge?
Aha! currently supports automations that trigger when a single child record changes state (e.g., “If an epic becomes At Risk → mark the parent initiative At Risk”). However, Aha! cannot support the inverse logic — resettin...
Guest
7 months ago
in Automations
0
Future consideration
I want dashboard panels to correctly reflect hidden columns from the list report
What is the challenge? I create a list report and hide columns. The columns being hidden are because i have calculated columns using these columns. I add the list report to a dashboard, but my hidden columns appear on the dashboard which i do not ...
Guest
5 months ago
in Reports
1
Future consideration
Show child initiatives nested under parent initiatives on the strategic roadmap
We have initiatives with child initiatives and those child initiatives contain releases, epics and features. The child initiatives are in a separate workspace line from the parent initiatives. The Strategy>Initiatives>Roadmap view works fine...
Guest
almost 5 years ago
in Roadmaps
4
Future consideration
Enable Elle Chats to be a referenceable record type
What is the challenge? Elle chats contain important context that may be useful to future chats on similar subjects.
Describe your idea.
Allow the entire chat session to saved as a record within Knowledge to enable future Elle sessions to refere...
What is the challenge? Recently Aha! released a great feature to create planning scenarios in Gantt views and Strategy Roadmaps. These aren't supported for custom roadmaps
What is the impact?
Teams that predominantly use custom roadmaps don't h...
Terence Osmeña
5 months ago
in Roadmaps
0
Future consideration
Hi, would you consider integration with Miro, formerly RealTime Board? This is a great diagraming app, and has a good Jira integration which I was going to use in a convoluted way by pushing from Jira to Aha to get visibility back in Aha. In reali...
Guest
almost 7 years ago
in Wanted / Whiteboards
18
Future consideration
What is the challenge?
In it's current state triggers for automations if you want to add multiple conditions only support "and", you can't do multiple "or" triggers.
What is the impact?
This requires you to make one automation to every one...
Guest
6 months ago
in Automations
0
Future consideration
Enhance the Audit History API to provide complete user information for both custom User-type fields and system User-type fields. For custom User-type fields, in addition to the existing raw_value (user IDs), expose the corresponding user email addresses (similar to the email_value field returned by the entity retrieval APIs). This would eliminate the need for additional user lookup API calls and keep the Audit History API consistent with the entity retrieval APIs. For system User-type fields (such as Assigned To, Created By, etc.), enhance the Audit History API to expose the underlying user identifiers and email addresses, rather than only the display names. Providing user IDs and email values would enable reliable processing of audit records, avoid ambiguities caused by duplicate display names, and offer a consistent experience across all User-type fields. These enhancements would improve API consistency, reduce integration complexity, and make audit history processing more reliable for customers integrating with Aha!.
What is the challenge? The Audit History API currently provides limited information for User-type fields. For custom User-type fields, it exposes only the user IDs (raw_value) without the corresponding email addresses. For system User-type fields ...
Guest
about 2 months ago
in API
0
Future consideration