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
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
Currently, when you change the type of record for an integrated record in ADO, it somewhat breaks the integration. Updates are still sent from Aha! to ADO but updates are not processed from ADO to Aha! It appears this scenario is supported for Jir...
Guest
12 months ago
in Integrations
0
Future consideration
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...
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
about 10 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
about 5 years ago
in Jira
0
Future consideration
Expose error messages from Developer Tools to front end on Zendesk integration
When connecting a ticket to an idea via the ZenDesk integration, sometimes you receive an error. This could be because: The user who authenticated the integration created the idea so has already voted The user who authenticated the integration no ...
Madeleine Black
about 7 years ago
in Integrations
0
Future consideration
Integrate Master Features and related features to different JIRA projects
In this scenario, there is one Program product workspace in Aha! and one Program project in JIRA which contains Master Features per Agile Release Train. All Stories (Aha Features) and sub-tasks (Aha Requirements) are with one or many Agile Teams (...
Guest
about 6 years ago
in Jira
1
Future consideration
What is the challenge? We leverage Adobe Analytics for a lot of analytics and reporting. It would be great to have a direct non-third-party integration. What is the impact? Allowing for synergy between our goals and roadmaps in Aha! and our report...
Guest
about 1 year ago
in Integrations
0
Future consideration