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...
When configuring a new Product in Aha to integrate with Jira: The backlogs are already in priority order in Jira. However, when syncing over to Aha!, the priority order does not carry over upon the first sync. I understand how to use the rank fiel...
Guest
almost 6 years ago
in Jira
1
Future consideration
I'd like to export (or even better: sync) my Aha todos with Todoist via Zapier.com or Built.io. Zapier supports the webhook API, but To-dos are not listed a record type for which a callback can be done.
Tako Bruinsma
over 9 years ago
in Slack / To-dos
0
Unlikely to implement
We want to show a dependency of one of our Features on a deliverable from another team without having to create a separate feature and map and sync it through the regular JIRA integration. I think being able to import the JIRA link (and descriptio...
Guest
over 8 years ago
in Jira
2
Unlikely to implement
The "Update Records" feature currently updates all integrated records defined in the Azure DevOps integration. This could take quite some time if the number of records is high. Sometimes you only want to upgrade on a particular record type because...
Support sending the Aha! Rank to Rally Rank in the 2.0 integration
Currently, the 2.0 integration does not support sending the Aha! rank to Rally in the same manner as the 1.0 integration - it cannot actually affect the ranking of items in Rally. As a customer who was using this in 1.0, we would like it to be ava...
Guest
almost 8 years ago
in Rally
1
Future consideration
It would be helpful if there was an API option to link existing records when migrating from Jira server to cloud. When migrating 00's of integrations we'd like to automate as much as possible.
Guest
12 months ago
in Integrations
0
Future consideration
Raise authentication errors from the update configuration process to the integration log
What is the challenge? Authentication issues are not called out when they occur during the reload configuration process. What is the impact? The user thinks they have successfully reloaded the configuration from Jira but the authentication may fai...
Mark Crowe
12 months ago
in Jira
0
Future consideration
Who would benefit? aha admins What impact would it make? keeping Aha in sync with JIRA on the release. This would also help other internal stakeholders informed. How should it work? The integrations import desperately needs additional filtering cr...
Shri Iyer
almost 2 years ago
in Jira
0
Already exists
When integrating AHA / Jira the field mapping only shows fields that can be editable. We are looking to bring in Created Date and Resolved Date on both the Jira epic and Jira story. These fields are dynamically created and populated based on the f...
Roger Octobre
almost 5 years ago
in Jira
0
Future consideration
Allow users to refresh all Aha! features from a linked JIRA integration.
Currently, only the changes made to a JIRA issue are sent over to Aha! through the webhooks. We should have a way to force Aha! to synchronize all descriptions and fields from JIRA for an entire release.
Alex Bartlow
almost 10 years ago
in Jira
0
Already exists