Adjust sync direction for URL fields in integration mappings
What is the challenge? When a URL custom field is referenced within field mappings of an integration, it can not be set to update from the integrated system to Aha! only from Aha! to the integrated system. What is the impact? We can not adjust dir...
Kristina Gass
3 months ago
in Integrations
1
Future consideration
Synchronize Aha! organizations custom field with Jira Integration
What is the challenge? We heavily use the Organizations custom field in Aha to map customer engagement and roadmap transparency and need that info to sync to our Jira instance. What is the impact? Disconnected systems, duplicate data entry, poor u...
I know that Aha includes the ability to attach documents at the Product Level. However, at my company, we want to maintain Policies & Procedures, but take advantage of the version control available in SharePoint. We want to link or integrate a...
Karen Wittenberg
over 7 years ago
in Integrations / Notes
7
Future consideration
It would be great if there is native integration of Aha.io with a Cisco Webex Teams bot much like the current Slack bot that is already available on Aha. Lots of users don't use email now and Teams is a great way to get notifications of posts and ...
Joshua Reola
over 6 years ago
in Integrations / Wanted
2
Future consideration
Map github username with aha emails for github-aha integration assignees sync
What is the challenge? aha-github assignees integration do not work What is the impact? cannot make use of the assignees sync in the integration Describe your idea In the Aha! Github integration the assignees are not getting synced. In Github we h...
Ankit Bapat
7 months ago
in GitHub
0
Future consideration
Manual Sending of Requirements to integrated development tool
Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
I R
over 1 year ago
in Jira
2
Future consideration
Make the standard tags field mappable for requirements
Both epics and features have the standard tags field mappable when setting up an integration. Requirements now have a standard tags field added to the record but it is not available in the mappings. It currently requires a custom field be created ...
Justin Waldorf
over 2 years ago
in Integrations
3
Future consideration
Bi-directional support for Area Level fields in ADO integration
What is the challenge? Currently we offer Area Level fields in our ADO integration for each Area Level. This allows us to receive the unique Area Level from ADO, but currently updates in Aha! do not change the Area Level back in ADO despite the se...