You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're currently trying to add a few automated update utilities to our frameworks, for example for automatically setting the automation status of test cases. We know that it is possible to update many work items in a single batch request, as specified here or here. The endpoint also does what it's supposed to do (verified in Postman).
Unfortunately, this neat library does not provide such a method in the WorkItemTrackingApi. There is only a function for updating a single work item and for retrieving work items in a batch request.
Would it be possible to add a function for updating work items in a batch request, as specified in the documentation?
Hi @csvtuda! Thank you for reaching out regarding this enhancement. We are currently working on higher-prioritized issues, but we will get back to this one as soon as we can.
Hey there,
We're currently trying to add a few automated update utilities to our frameworks, for example for automatically setting the automation status of test cases. We know that it is possible to update many work items in a single batch request, as specified here or here. The endpoint also does what it's supposed to do (verified in Postman).
Unfortunately, this neat library does not provide such a method in the
WorkItemTrackingApi
. There is only a function for updating a single work item and for retrieving work items in a batch request.Would it be possible to add a function for updating work items in a batch request, as specified in the documentation?
As far as I can see, this was never discussed: https://github.com/microsoft/azure-devops-node-api/issues?q=work+item+batch+
Environment
Node version: v18.12.1
Npm version: 8.19.2
OS and version: Windows 10 Pro 22H2 19045.4291
azure-devops-node-api version: 13.0.0
The text was updated successfully, but these errors were encountered: