Integrations
Sort by:
Trending
Status:
Future consideration
Showing 642
5
VOTE
Ability to customize the Import Import New Records dialog box and functionality
It would be very helpful to be able to customize and configure the Import New Records dialog box. Specifically I would like to be able to select additional/different information about each record (i.e. Azure DevOps work item #, State, Iteration) i...
0
Future consideration
6
VOTE
Integrations Update Window- Rules & Scheduling Ability
We need the ability to set rules for the integrations update window (found in the settings gear) to specify what types of records we would like to import and when. This would allow for scheduled imports and filters on data attributes (such as stat...
4
Future consideration
3
VOTE
Integration between Aha! and Jira Align (formerly Agilecraft)
Jira Align is a requirements tracking platform that was formerly Agilecraft, and is fully integrated with Jira. Our teams that are using both Jira and Jira Align are mapping their Epics in Jira to parent Epics in Jira Align, so that the roll-up pr...
1
Future consideration
3
VOTE
Allow mapping Release as a field on Requirements in Azure DevOps integration
Due to our iterations setup in Azure DevOps (ADO) we do not currently map Releases as a record. We are sending this instead as a field on the Epic and Feature records to a custom field in ADO. We would like to do the same on Requirements but it is...
0
Future consideration
2
VOTE
Allow scheduled update of all linked records for DevOps
As the service hooks from DevOps to Aha are seldomly failing, it often results in having some records not in sync in Aha. This can be solved by running an update of all the linked records from the Aha integration page, but this requires to be manu...
2
Future consideration
5
VOTE
Enable Field Filters for when to Sync to Aha
I would like to be able to set a filter in my Integration for which Jira Issues to sync up. An example would be to not push stories into Aha until there is a point value or time estimate entered in Jira. Another would be to only push to Jira if it...
0
Future consideration
1
VOTE
Inform user if Version export to Jira fails due to existing fix version in Jira
Problem If a Version is exported from Aha to Jira using the integration, and a fix version with that same name already exists in Jira, Jira will response with HTTP status code 400, and a JSON payload: {"errorMessages":[],"errors":{"name":"A versio...
0
Future consideration
2
VOTE
Integration Log "Type" Filter
As a workspace admin viewing the Integration Messages Log - I'd love to be able to click these buttons at the top of the log to filter just to "Errors" in red, "warnings" in yellow or "info" in blue - currently most updates are "info" and importan...
0
Future consideration
2
VOTE
Full 2 way integration for ZenDesk
We use ZenDesk as our Support Desk for our product, allowing our Support team to raise bugs or issues to investigate with our Dev team to look at. These range from low priority issues to high priority issues. We would like to use Aha Develop to ru...
0
Future consideration
2
VOTE
Default workspace name filter in integration updates screen
In order to limit the information displayed in the integration updates screen to be more relevant, set the workspace name filter to default to the workspace chosen in the application rather than defaulting to show all
0
Future consideration