check against an updated list in azure devops

[Amalie1]

Hello,

I have just created a flow where every time an email with attachment is sent to a shared mailbox, a user task will be created in Azure Devops. Here I have specified the title should be that of the file. I was wondering if it is possible to set up a condition that would check the title of the file from the email, against the titles in Azure Devops? So that it is not possible to create the same item multiple times.

Best,

Amalie

[Expiscornovus]

Hi @Amalie1,

You can use a WIQL query for this in a Send an HTTP request to Azure DevOps action.

Below is an example

This is the WIQL query. In this WIQL query I check if the work item exists in a specific project based on the Title and the WorkItemType.

{
"query": "SELECT [System.Id],[System.AssignedTo],[System.State],[System.Title],[System.Tags],[System.WorkItemType] 
FROM WorkItems
WHERE ([System.WorkItemType] = 'Task') AND ([System.Title] = '@{triggerOutputs()?['body/attachments'][0]['name']}')"
}

This is the condition expression

length(outputs('Send_an_HTTP_request_to_Azure_DevOps')?['body']['workItems'])

is equal to 0

[Amalie1]

Hi!

Thank you for your reply. This is the structure of my current flow. Would you put the query 'Send an HTTP request to Azure DevOps' before or after my 'create a work item'?

Also, I see you have an expression called 'initialize variable', should I also include this or have you just used it to be able to showcase the other queries?

Best,

Amalie

[Expiscornovus]

Hi @Amalie1,

The new action(s) are added before the Create a Work item action. 

I have added the Send an HTTP request to DevOps and a Condition action and moved the Create Work Item in the If Yes section.

The variable action is just to store the name of the project. I have expanded that action in a new version of the screenshot, if that helps.

[Amalie1]

I have now made my flow run using your suggested query, however, it still creates the same work item even though it already exists within Azure Devops. DO you have any idea why that is? 

[Expiscornovus]

Hi @Amalie1,

Can you share a screenshot how you have configured the flow? Can you also share a screenshot of the outputs of the Send an HTTP request to DevOps action. It is useful to see what that query did (or did not) find.

[Amalie1]

Sure, here it comes:

Outputs:

[Expiscornovus · Accepted solution]

Hi @Amalie1,

In the Send an HTTP request to Azure DevOps action you are checking if a Task already exists. However, in the create work item you are creating a User Story. That is the reason why it cannot find the duplicate, it is looking for tasks, not user stories in the query.

Please update the Body of the HTTP request to the below to filter for User Story instead.

{
"query": "SELECT [System.Id],[System.AssignedTo],[System.State],[System.Title],[System.Tags],[System.WorkItemType] 
FROM WorkItems
WHERE ([System.WorkItemType] = 'User Story') AND ([System.Title] = '@{triggerOutputs()?['body/attachments'][0]['name']}')"
}

[Amalie1]

Thank You! It works! You have been such a great help :))