Integrations
Sort by:
Trending
Status:
Future consideration
Showing 647
2
VOTE
Azure DevOps or JIRA integration : allow some way to automatically select which integration to use when more than one exists in a product
We usually map 1 Aha Product to 1 AzDo project, in which case everything is fine (except that everything ends up in the same Area Path). We can also easily map N Aha Products to 1 AzDo project, mapping each Product to an AzDo area path. But we cur...
0
Future consideration
2
VOTE
Allow for a check list to be copied to the GitHub product AND not change the check list in the originating work activity.
The check list (versus ordered / unordered list) in the text field is very nice. However, integration process translates the Check List to an unordered list in GitHub and then updates that back to the originating work activity. This process change...
0
Future consideration
2
VOTE
Integrate with 3rd party digital marketing tools API
Importing campaign data from the many different marketing tools we digital marketers use every day can be time-consuming and a little frustrating. In order to monitor meaningful digital ad campaign results that do not show up in Google analytics (...
0
Future consideration
1
VOTE
2
VOTE
Exclude users for activity webhook
To help with creating integrations between systems.
The specific case would be an automated system that keeps aha synchronized with an external system. The system needs to log in as an user to make updates, but the system does not need to see web...
0
Future consideration
2
VOTE
Add Ability to not send a specific release to Rally on Master Feature or Feature
Rally has a concept of Backlog where the Release is set as 'Unscheduled'. But there is no way in Aha! to assign a Master Feature or Feature to something like 'Unscheduled' so that the Release information does not get populated in Rally. We want to...
0
Future consideration
2
VOTE
Add Product Prefix field as a choice in the JIRA integration
We integrate Aha! with multiple JIRA projects and often use the product prefix as the Component to identify the source of the ticket. Today we use a constant and add that manually. Adding it from the prefix would save us a lot of time!
0
Future consideration
1
VOTE
2
VOTE
Allow for "approve incoming changes" in Jira integration
There is currently an option to approve outgoing changes or incoming records, but not incoming changes.
The current options are:
- Allow any Jira user to directly impact sensitive Aha roadmap information by changing Jira tickets (we map Epics to...
0
Future consideration
2
VOTE
Rally integration at task level
In Rally, Features have a release assigned to them, but each user story from that feature will have it's own release assignment as well. Tasks added to a user story will always follow the release from the user story.
In Aha, Features have a relea...
1
Future consideration