Integrations
Sort by:
Popular
Status:
Unlikely to implement
Showing 129
2
VOTE
2
VOTE
Support iovation LaunchKey for Multi-Factor Authentication
Currently you seem to only support stronger authentication options for those customers who use Duo (under their own contract). While we would be OK with an Aha! contracted strong authenticator, if we must supply our own then our preference would b...
0
Unlikely to implement
2
VOTE
JIRA and Aha synchronized numbering
We understand that the IDs in AHA and JIRA are meant to be treated as separate IDs without a true association between the two systems. However our workflow allows us to use the same IDs in both systems, assuming we enter them in the same order. Ho...
0
Unlikely to implement
2
VOTE
2
VOTE
Would it be possible to not need a paid AHA account to process VSTS updates?
At the moment we have set up the VSTS integration with a paid AHA account as required. This means that all updates come in from that product manager. In the history threads, and the notification emails we get a combination of VSTS updates, and the...
1
Unlikely to implement
2
VOTE
Github issues to get Aha feature ID in their name
We typically reference feature requests by the Aha feature ID, e.g. WEB-32 or WEB-44. When we push those feature requests down to Github for development, we generally create a branch for each issue, but since we lose this information it's difficul...
2
Unlikely to implement
2
VOTE
2
VOTE
Add prefixes to feature stories in Rally
When integrating with Rally using the "Feature -> User Story, Requirement -> User Story" mapping, it would be great if we could give custom prefixes to the feature stories names in Rally without having those prefixes displayed in Aha.
We us...
0
Unlikely to implement
2
VOTE
2
VOTE
