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...
Re-enable conversion of Features to Requirements when JIRA integration is active
In some cases, people add stories in JIRA for a release linked to Aha that are not part of an Epic. This can result in the JIRA story appearing in Aha as a Feature (at the same level as JIRA Epics), due to how the integration is set up. Previously...
Light grey text is illegible to visually impaired users
Currently, in an integration, when the settings are locked (e.g. the project to which it is integrated) the text is shown in a light grey to indicate the settings cannot be changed. This creates a challenge for users who are color blind or otherwi...
Add missing Rally built in fields "Project" and "Leaf Story Plan Estimate Total" in Aha! under Integration field mapping
The following fields are available in Rally but are not available in Aha to do field mapping under Aha to Rally Integration. Please add these fields so that teams can map them. Rally Built in field names: Project Leaf Story Plan Estimate Total
Right now you can only define default values for TFS fields. It would be better if there was a way to map fields in AHA to fields in TFS, including custom fields. This could be done by using variables (aka: {{Assignee}}) in the current UI or provi...
Add support for linking to multiple different JIRA issue types
We would like to roadmap product releases with new up-coming features and bug fixes. Aha features currently map to Jira stories but we'd like to map to Jira 'Bug' and possibly 'Improvement' types as well.
Integrations 2.0: Selectable behaviour for importing new records when multiple Aha! products integrate with a single JIRA project.
Often teams will integrate multiple Aha! products with a single JIRA project. Currently the import behaviour in 2.0 is you get 'n' number of import candidates which appear in the "Import New Records" modal for all integrated Aha! products regardle...
Mark linked Jira tickets that have been deleted in Aha
I noticed that when deleting a feature in Aha! that is linked to Jira, Aha! doesn't delete the linked ticket. I disagree with your design decision, but the message from support makes it clear that you're firm in that direction. Still, when an Aha!...
Map feature "Value" field in Salesforce integration to a custom field instead of the opportunity value
We need a tool that helps us quantify the potential value/ROI of a feature (to the extent that this is possible...). The SF/Aha! Integration ties to the standard opportunity amount field in SF, but that field is not the metric that we care about i...
Improve Component mapping in Jira and updated error handling
What is the challenge? When mapping Components in Jira to a predefined choice custom field in Jira, you are not given the option to map the values. If there is a failure in the import due to this field, no record or error information is displayed....
Move epic/feature to default release when integrations unlink the release
What is the challenge? When an integrated epic or feature is moved in a dev tool (Jira or Rally) to an "unscheduled" release, the relationship in Aha! is null and no change occurs. This is problematic because the release was changed but the Aha! r...
Jeanette Resnikoff
12 months ago
in Integrations
1
Shipped