Integrations
Sort by:
Trending
Status:
Unlikely to implement
Showing 146
1
VOTE
There is not currently a mechanism to create a report for the "Send outgoing" or "Import new records" Integration Updates tabs.
There is not currently a mechanism to create a report for the "Send outgoing" or "Import new records" Integration Updates tabs.
Can we provide a mechanism to generate this report to make sure all the products at utmost sync with integrated systems
0
Unlikely to implement
1
VOTE
A way to execute saved queries, or use a query language (such as the filter options in the web UI) with REST
This would allow users of the integration to narrow down the scope of items being retrieved to improve performance and create less unnecessary traffic on the Aha! repository.
0
Unlikely to implement
1
VOTE
Integration should be deleted, rather expired
The items impacted by the deleted integration of Feb 20 are still intact (prior releases leading to current release PI01 included).
The integration we created as new is handling the new items targeted for our next release PI02.
Side note:
- ...
1
Unlikely to implement
1
VOTE
JIRA integration: support mapping of “Release name” into custom field
Mapping of “Release name” towards custom fields in JIRA integration instead of “fixed version” or “affected version” only
currently the AHA-Jira integration only allows a mapping of "release name" values in either "fix version" or "affects versio...
1
Unlikely to implement
1
VOTE
Aha should support multiple "types" in Jira (epic, bug, use case, tasks) in one single Aha query
Hortonworks uses following Types in Jira application: Epic, New feature, PRD, Tasks, Doc.
Currently, we have to create multiple queries using Development tool in order to bring the above Jira tickets to Aha.
Requirement: The query should bring a...
0
Unlikely to implement
1
VOTE
Add batch API endpoints for Add, Update, and Delete interactions
As a heavy user of the REST APIs to aggregate and disseminate information across multiple systems, I would like to have a batch API endpoint for updating Features in order to avoid Throttling limitations in the existing one-update-at-a-time REST i...
2
Unlikely to implement
1
VOTE
add NetIQ Access Manager by Micro Focus to INTEGRATIONS – SINGLE SIGN-ON
Our team at Micro Focus has created a generic SAML connector for Aha! that can be used with our product, NetIQ Access Manager. It can be downloaded from our catalog, http://catalog.netiq.com/ncarest/displayCatalog?type=saml
Now, customers who us...
0
Unlikely to implement
1
VOTE
New Integrations with ConnectWise and Netsuite
We use CW as a CPQ tool. It would be great to be able to import quotes into our product builds this way. We use netsuite for all sales related tasks. It would be great to be able to get lists of what is selling into Aha! so we can prioritize resou...
0
Unlikely to implement
1
VOTE
TFS Integration, match user for "assigned to" field
Aha! takes my email address as user name but TFS requires <DOMAIN>\<Last Name> as user name. Therefore the integration throws errors when an Aha! user is set in the TFS "Assigned to" field of a feature.
My suggestion to solve this is t...
3
Unlikely to implement
1
VOTE
