Integrations
Sort by:
Trending
Filter by:
Status
Showing 929 of 8757
2
VOTE
Support creating a Requirement from Zapier
It's possible to create Features and Ideas based on triggering events in Zapier, but often it's the Requirement level in Aha! that gets mapped to individual stories in other tools, not Features.
It should also be possible to have Zaps that will c...
0
Unlikely to implement
2
VOTE
Support adding an integration id to a new feature/idea from Zapier
It's possible to create a new Feature or Idea in Aha! when something happens via Zapier (eg Trello card or GitHub issue created), but there's no way to link the new artifact back to the triggering artifact, even if the triggering item is in a conf...
0
Unlikely to implement
2
VOTE
Sync @ Mentions With Linked JIRA Users
Useful to keep users of JIRA and Aha in sync between systems without managing Watchers across installations.
I've noticed that @ mentions in Aha! do not match the JIRA username on comments. I want to ensure that JIRA users are notified when I @ m...
0
Unlikely to implement
1
VOTE
Ability to execute a AzureDevOps query and display results in charts on Aha Dashboard
For the teams who uses AzureDevOps as ALM tool , It would be great flexibility to view a snapshot of the query results on the Aha dashboard. It does not need to be sync but can be pulled async.
0
Future consideration
2
VOTE
Add idea integration with Parature
We use parature as our system for managing customer support tickets including logging bugs. We would like the ability to push customer logged bugs from Parature directly to Aha so that customers can be made aware of bugs logged by other customers,...
0
Unlikely to implement
1
VOTE
Allow TFS integration to map bidirectionally for fields that are not in a built-in System.State.
Currently, the TFS integration does not support mapping arbitrary string fields to the Aha! workflow status field in a bi-directional way. Only the built-in System.State field in TFS can be mapped bidirectionally.
2
Future consideration
1
VOTE
2
VOTE
1
VOTE
Release Should Be Marked as Shipped only when all Integrations for JIRA projects are shipped
If multiple integrations are enabled at release level, allow workflow rule for release to be considered as shipped when all integrated JIRA projects have shipped the release If someone marks the release as shipped in JIRA, its changing the status ...
0
Unlikely to implement
1
VOTE
