Features and Epics should move to integrated parent Release upon updates
What is the challenge? If you introduce Version<>Release mapping to an existing integration or you link a record to an existing Jira record, subsequent updates are creating a new Aha! release (linked to the Jira issues's Fixed Version) but t...
Stephanie Lechner
2 months ago
in Jira
0
Planning to implement
What is the challenge? There is no easy way to send ideas to engineering to work on or keep the information in sync. What is the impact? Time spent copy and pasting data. Out-of-date information leading to confusion. Describe your idea Like the re...
Integrate Aha! and Confluence to link Confluence Pages in AHA! and transfer them with JIRA
Atlassian currently offers the ability to Integrate Confluence & Jira using Application Links which gives teams multiple features. https://confluence.atlassian.com/doc/use-jira-applications-and-confluence-together-427623543.html One of the fea...
Tyson Kretschmer
over 7 years ago
in Integrations
6
Future consideration
Seamless Sync for Epics and Features Between Aha! and ADO when changing types
What is the challenge? Currently, when an Epic is changed to a Feature or vice versa in Azure DevOps (ADO), this change is not accurately synced with Aha!, leading to misalignment and inefficiencies. What is the impact? Epics and features are misa...
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
16 days 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
16 days ago
in Jira
0
Future consideration
It would be great to have a dedicated integration user instead of having to use a user license for this purpose. I would love to keep my user and the updates from integrations (Jira, TFS,...etc) separate so that it is clear who made the update in ...
Guest
over 7 years ago
in Integrations / Jira
16
Future consideration
Allow automatic imports of child records when parent records exist in a different workspace
What is the challenge? Currently, for Jira integrations, when you have parent/child records in Jira that span multiple Jira projects connected to multiple Aha! workspaces, all child records created will need to be manually approved as an integrati...
Stephanie Lechner
about 1 month ago
in Jira
0
Future consideration
Activity webhook triggered by a specific custom field
What is the challenge? Our custom integration between Salesforce and AHA is not being triggered. What is the impact? Custom field is not updated in SF when it is the only field updated on an idea. Describe your idea Allow activity webhook configur...
Hilla Shohat
about 2 months ago
in Integrations
3
Future consideration
What is the challenge? Ideas/Roadmaps integration with viva engage (yammer) similar to slack or teams integrations. What is the impact? We currently share updates from roadmaps and ideas with stakeholders and teams via yammer rather than teams. De...
Simone Bilton
about 2 months ago
in Integrations / Wanted
0
Future consideration