Today, the SFDC integration can only link opportunities to ideas. It would be great to also link to features. This could help prioritize features that are still in a parking lot and would reduce the buden of merging ideas created via SFDC with exi...
Fabien Maisl
over 5 years ago
in Salesforce
2
Future consideration
Enhance MS Teams Integration- Support 2 Way Integration
Given that MS Teams has significantly expanded its functionality over the past year to include features such as Document Storage, it would be beneficial to have 2 way integration with MS Teams. Two-Way integration would allow features such as:
1. ...
Josh Tambor
over 4 years ago
in Integrations
4
Future consideration
Text from Azure DevOps into custom fields shows with HTML elements
What is the challenge? When syncing a "text" custom field with Azure DevOps it shows the text with HTML elements What is the impact? It makes the custom field text difficult to read Describe your idea Ensure text custom fields convert HTML tags wh...
Ability to create a report of integration errors across multiple workspaces
Currently the only way to look at the integration errors across multiple workspaces is to bring up the Integration Updates dialog and use the Send outgoing changes tab. But you can't filter on error text, or expand the window to see the everything...
Jor Bratko
about 3 years ago
in Jira
5
Future consideration
When, for example, an idea is created within aha! and the integration alerts a slack channel of this entry, it would be good to be able to customise the output of that notification and remove unwanted fields.
Guest
over 3 years ago
in Slack
2
Likely to implement
I have set up Aha to integrate with Jira (development team) and Looper (field team), I would like to be able to have a seemless "automated" way to link comments and status between ideas and features. The idea being when Jira development teams have...
Chad Tidd
over 4 years ago
in Integrations
0
Future consideration
Ability to import child records when connecting to an existing record in Jira
What is the challenge? We often have the use case where we need to connect an Aha! epic to an existing Jira record, and that Jira record will also likely have child tasks/stories. The existing connection logic will only sync with the epic record, ...
Nerissa Muijs
4 months ago
in Jira
0
Future consideration
For security reasons, we cannot have Aha! set to "allow anyone to access." Still, we need the ability to provide a seamless experience for our Executives and users to derive value from the Aha! data. We want to be able to display these in Tableau ...
Guest
over 1 year ago
in Wanted
2
Future consideration
Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...
Guest
almost 2 years ago
in Jira
1
Future consideration