Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 108

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.
Guest over 4 years ago in Azure DevOps Services and Server 2 Future consideration

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...
Sekhar Nallapaneni about 5 years ago in Azure DevOps Services and Server 0 Future consideration

Automatically create webhooks by default for Azure/TFS

No description provided
Guest over 5 years ago in Azure DevOps Services and Server 0 Future consideration

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...
Tom Beck almost 6 years ago in Azure DevOps Services and Server 1 Future consideration

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 (Requirements...
Sekhar Nallapaneni almost 6 years ago in Azure DevOps Services and Server 1 Already exists

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.
Brian W over 6 years ago in Azure DevOps Services and Server 4 Already exists

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...
Guest over 6 years ago in Azure DevOps Services and Server 3 Unlikely to implement

Bulk Delete for files , and don't default to ADO integration - Attachments

Whoops. I accidentally set up the ADO integration to include attachments, and now I've got hundreds of ADO development files in my beautiful AHA portal "Workspace Files" section. I've now switched off the attachment synchronization, but left with ...
Guest over 4 years ago in Azure DevOps Services and Server 0 Future consideration