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...
Sometime companies use customized templates with custom work item types. Currently the ADO integration only supports integration with the standard types like "initiatives", "features", "Requirements". Our template supports a custom type called "PI...
Integrated icon or color on release column of board views to show integration linked
My users are expected to help keep their roadmap releases integrated to the tools of the engineering team (jira or Azure Devops). They need to link the release to the jira release or ADO iteration path, to keep roadmaps and scope alligned in both ...
Guest
over 2 years ago
in Integrations
0
Future consideration
The ability to create a report to show if there are any pending Integration Updates rather than having to manually look for them
Simplify the ability to know if there are pending updates to either Import or Ignore by running/scheduling a report with this data by Workspace and Integration, etc.
Guest
over 2 years ago
in Jira
0
Future consideration
Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship.
Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship. Same like Jira we have parent -child relationship concept of subtask we need in Aha same functionality.
We use the Github integration for a few of our projects. I have it configured to import Features to Issues and Requirements to Issues.
It would be very helpful to exclude some records during the import process. For example, I recently sent a Featu...
Guest
about 7 years ago
in GitHub
2
Future consideration
Better presentation of text when integrating to an existing field in ADO
Sometimes, the feature in ADO already exists, and I want to link it to a feature in Aha. When I do this, I'm presented with an un-readable HTML output of the description fields, making is pretty much impossible to actually see the differences. See...
Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features
Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
Dale Potter
almost 5 years ago
in Jira
0
Future consideration
Stories that are pushed to Rally from the Aha Parking Lot are creating a release in Rally titled Parking Lot. I would like to see these user stories not be assigned to a release in Rally, that way they will be be displayed on the backlog.