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...
We’ve got users landing on pages that have been disabled on their main menu when they navigate between workspaces. This causes some issues when rolling out Aha widely as an ‘intuitive’ self serviceable tool. An example is: Going to a workspace def...
William Wang
about 4 years ago
in Application
0
Future consideration
It is a dynamic world. Sometimes it is better to delete a product and later on possible to reuse its prefix? (have to admit that this is due to the start up of product management, but everyone who starts will be confronted with this issue?)
Thx
Nic
Make Notes, available as a relationship custom field
We use notes to capture information related to the EPIC. While there are other custom fields that can be added natively to an EPICS's layout Notes is not one. The only way I've seen to attach a NOTE to an EPIC is making it RELATED. The issue with ...
Eugene Peters
about 4 years ago
in Epics / Notes
0
Future consideration
Annoying maintenance task of updating expired webhooks that keep making systems out of sync and we end up using VSTS as the source of truth rather than Aha!
In 1.0, when using a template, you could choose what fields/behaviors to inherit from the template, and which to customize for that particular integration. This was useful for custom fields (now using a constant in 2.0) which will change from prod...
Max Cascone
about 8 years ago
in Jira
6
Already exists
Addition of one or more custom field in the requirement section within the Features
Since Bugs are not 'first class' entities in Aha and the suggested workaround is to map requirements with bugs in JIRA, we have done that and use a custom field of type in requirements which has the value of bug and story. However, when we open a ...
Arun Kalyanaraman
about 4 years ago
in Features
0
Future consideration
Delete To-Dos without needing to dive into details
It would be more intuitive to be able to delete To-Do's from the view you see them in, instead of needing to go into detail view to delete each specific one.
Asim Dhital
about 4 years ago
in Releases
0
Future consideration
Enable side by side of epics and features on Features page
In the board view for Features, you can pivot between epics and features. I would like to be able to see a view where epics are on the left and features are on the right, enabling simple drag and drop of features into an epic. We often start off w...
Jennifer Briden
about 4 years ago
in Features
0
Future consideration
It's helpful to be able to measure the complexity / effort of work compared to the value we expect it to bring to our users. While setting this for initiatives is useful, we also need to be able to do that for Epics and Features.
Jennifer Briden
about 4 years ago
in Features
0
Future consideration