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.
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...
DevOps Integration issue with multiple attachments default name Image.png
See the support request# #408720 for the integration error with for a work item with more than one attachment with same name. Resolution provided by Aha! support is to rename the image.png files differently so that DevOps accepts them. Can Aha! Im...
ability to integrate idea information into Azure DevOps
We use the ideas portal to solicit new enhancements from our users and then link those ideas to features in our products. The problem is only our product management and dev management use Aha. our development team uses Microsoft DevOps to track th...
Converting requirements to features after integration
Converting a requirement to a feature will cause the record to lose some custom field information because features may not have the same custom fields. We can choose whether or not to proceed. There's no mention of integration to an external syste...
VSTS Integration - Error importing new records into Aha
As we are starting to use more and more Aha!, we are seeing errors while newly created records by Development team in VSTS being imported into Aha!. 2 main reasons for the errors include
Feature is not available for the user stories (Requiremen...
when syncing master features and linked features to VSTS, have relationship between these items persist on the VSTS Side
Here is issue:
Create Epic in AHA
Create Feature in AHA, linked to Epic above
Sent Epic from AHA to VSTS
Sending Epic to VSTS does also automatically send the Feature from AHA to VSTS. However, the Epic and Feature in VSTS are not linked.
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...