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...
Include history of comments when importing from ADO integration
What is the challenge?
Currently, when importing ADO records via an ADO integration only the latest comment is imported from ADO
What is the impact?
Inability to see comment history can lose critical context and require Aha! users to go to...
Ability to Configure Epic View as Default for all workspace views (Board / Prioritization)
Who would benefit? Enterprises who maintain Epic only or use Epic as primary record type. What impact would it make? Reduce confusion. The teams are currently directed to feature view on the board and prioritization view by default. Per Aha concie...
Guest
about 2 years ago
in Epics
0
Planning to implement
The release gantt chart has good functionality, but does not offer the opportunity to add custom fields. In my case, I can avoid duplication of reporting in an outside tool if I can show two custom fields for the features.
Guest
about 5 years ago
in Reports
1
Future consideration
The ability to have a tool tip for a standard field
Aha Score is a standard field in Aha and like many others, you still can configure it based on your business requirements. This is why it would be good that the reviewers' users be able to understand the metrics under that score and have quick vis...
Guest
almost 6 years ago
in Account settings
4
Future consideration
Allow ability to limit valid values in Feature fields to only display relevant values for the workspace.
When defining features in a workspace, you should only need access to utilize valid values from selected workspaces. Each workspace owner defines and reports on their valid values very differently. When all valid values from every workspace are di...
Guest
about 4 years ago
in Account settings
1
Future consideration
View in Aha! the author of a comment created in Azure DevOps
In integrations with Azure DevOps, comments created in ADO show the integration name rather than the individual as the creator of the comment when looking at it in Aha!. This can cause confusion for Aha! users who can't easily understand the conte...
Guest
almost 5 years ago
in Integrations
2
Likely to implement
Integrations 2.0: Add dependency link to connect records without natural relationships together
In integrations 1.0 if I mapped Features = Story Requirement = Task Aha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other. ...
Danny Archer
about 8 years ago
in Dependencies / Jira
3
Future consideration
Being that we don't have a reliable user access management tool, our Admins clean up the users if no activity after 90 days. Unfortunately, there isn't a way to filter this, so I must click every user on the page in order to disable in bulk. Click...
Guest
about 5 years ago
in Account settings
1
Future consideration
Currently Aha! offers two data center options: EU and US. This is a suggestion to offer an India data center option for India companies who require this.
Guest
5 months ago
in Application
0
Future consideration