Azure Devops Connector - Create Work Item for Unassigned

[HenryKrinkle]

Hi there,

Just getting to grips with Power Automate and loving it 🙂  I've created a flow using the Azure Devops connector that in short creates child tasks when a bug is raised.

It works beautifully but I wondered if its possible to raise the tasks unassigned, rather than to my own user?

So far I have tried (with the create new work item step)

• Assigning the value of the Parent work item 'Assigned To' to a variable and using that in the 'Create Work Item' step.
• Leaving 'Assigned To' Empty or using a null value
• Using the Other Fields to set null values to Vsts_AssignedToEmail and System_AssignedTo field.

I'm struggling to find a reference to anything other than this article Cannot Create Work Item Through API When Unassigned Is Null - Developer Community (visualstudio.com), which I appreciate is not the same but does indicate the API would ignore assigned to if it is blank.

I cant really spot an answer in the connector documentation, unless i'm missing something?  It may simply be a case of its not possible without more work.

Thanks in advance.

[Expiscornovus · Accepted solution]

Hi @HenryKrinkle,

Which action are you using to create your task work item?

When I use the Send an HTTP request to Azure DevOps I am able to create unassigned tasks by using this body sample.

[
  {
    "op": "add",
    "path": "/fields/System.Title",
    "from": null,
    "value": "Sample task Unassigned"
  }
]

[HenryKrinkle · Accepted solution]

Hi @Expiscornovus ,

You're a star, thank you so much for the reply - I was using the standard 'Create A Work Item'.  Using your example I found I had to add this to the body and explicitly set the 'Assigned To' field to an empty string.

    {
        "op":"add",
        "path":"/fields/System.AssignedTo",
        "from":null,
        "value":""
    }

N.B All this was wwwaaaaayyyy out of my knowledge/comfort zone but I have learnt something about this connector, REST API's, Azure Devops and Postman so I am feeling well chuffed with myself.

Thanks once again.

HenryKrinkle

[Expiscornovus]

@HenryKrinkle, thank you for asking this question and great to hear that you learned a lot. Btw, I am also learning a lot from these type of questions 🙂

[mnshah]

Hello,
I am facing the same issue. After "Create a work item - azureDevops" I added another step "Send an HTTP Request to AzureDevops". Am I doing it right?

This is what I have:
Relative URL: https://dev.azure.com/[OrganizationName]/[ProjectName]/_apis/wit/workitems/$api-version=6.0
Headers: Content-Type: application/json-patch+json
Body:  {
"op":"add",
"path":"/fields/System.AssignedTo",
"from":null,
"value":""
}

Error Details:
No api-version was supplied for the "POST" request. The version must be supplied either as part of the Accept header (e.g. "application/json; api-version=1.0") or as a query parameter (e.g. "?api-version=1.0").
Azure DevOps ActivityId: xyz
Details: {"$id":"1","innerException":null,"message":"No api-version was supplied for the \"POST\" request. The version must be supplied either as part of the Accept header (e.g. \"application/json; api-version=1.0\") or as a query parameter (e.g. \"?api-version=1.0\").","typeName":"Microsoft.VisualStudio.Services.WebApi.VssVersionNotSpecifiedException, Microsoft.VisualStudio.Services.WebApi","typeKey":"VssVersionNotSpecifiedException","errorCode":0,"eventId":3000}
clientRequestId: abc

Thanks

[Expiscornovus]

Hi @mnshah,

You are missing the question mark character before the api version and you also haven't included the type value in your uri. If that still does not work can you create a separate thread, this one is 4 years old.

/fabrikam/{project}/_apis/wit/workitems/$task?api-version=7.1-preview.3

https://learn.microsoft.com/en-us/rest/api/azure/devops/wit/work-items/create?view=azure-devops-rest...

[mnshah]

Thanks for the reply
Here is the new thread with more details: (1) Azure Devops Connector - Create Work Item for Unas... - Power Platform Community (microsoft.com)