Azure DevOps Services and Server
Sort by:
Trending
Filter by:
Status
Showing 108 of 9040
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
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...
0
Future consideration
1
VOTE
1
VOTE
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...
1
Future consideration
1
VOTE
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...
1
Already exists
1
VOTE
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.
4
Already exists
1
VOTE
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...
3
Unlikely to implement
0
VOTE
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 ...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved