Unanswered

Adding the attachments to Azure DevOps work item in "Create a Work item" step

(2) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Hi ,

Is there a way to attach a certain file from email directly to the attachments section in the User story of Azure DevOps, I'm currently having a flow that creates a work item whenever tehre is a new email but can't able to process the attachments linked to it. I need those attachments in the user story itself. Can somebody help me??

Categories:

General topics

I have the same question (0)

All responses (64)

Answers (0)

yashag2255 24,769 Super User 2024 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Hi @Anonymous

Currently adding an attachment as a direct action is not supported in flow. However, you can refer to the thread below where a workaround has been suggested for creating the attachments:

https://powerusers.microsoft.com/t5/Building-Flows/Create-work-item-at-Azure-DevOps-from-an-email-with-attachments/td-p/176019

You can post an idea here to include this as a feature in flow:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Was this reply helpful? Yes No
TheSwilliam 40 on at

Like (7)

Report
Copy link

Link copied!
Make sure you name everything the exact same thing as what I have if you are copying and pasting from here. You will need to add in your organization name.
The schema is:

{ "type": "object", "properties": { "Id": { "type": "string" }, "Name": { "type": "string" }, "ContentBytes": { "type": "string" }, "ContentType": { "type": "string" }, "Size": { "type": "integer" } } }

Then
the binary function is:

binary(body('Parse_JSON')?['ContentBytes'])

Make sure you change the areaPath in the relative URI. I left it as mine which is just Portal.
Code snippet for the step above:
{
    "inputs": {
        "host": {
            "connection": {
                "name": "@parameters('$connections')['shared_visualstudioteamservices']['connectionId']"
            }
        },
        "method": "post",
        "body": {
            "Method": "POST",
            "Uri": "https://dev.azure.com/YourOrganization/_apis/wit/attachments/?uploadType=Simple&areaPath=Portal&fileName=@{items('Apply_to_each_2')?['name']}&api-version=5.0",
            "Headers": {
                "Content-Type": "application/octet-stream"
            },
            "Body": "@{binary(body('Parse_JSON')?['ContentBytes'])}",
            "IsBase64": true
        },
        "path": "/httprequest",
        "queries": {
            "account": "YourOrganization"
        },
        "authentication": "@parameters('$authentication')"
    },
    "metadata": {
        "flowSystemMetadata": {
            "swaggerOperationId": "HttpRequest"
        }
    }
}
Then
The 'Body' in 'Compose' is the body that you will get from the Http Post which I have named 'Post Attachment'
The 'url' is actually an output function:

outputs('Compose')['url']

The outputs function is getting the url property from the response json from Post Attachment.
Code snippets for the steps above:
Compose:
{
    "inputs": "@body('Post_Attachment')"
}
Compose 2
{
    "inputs": "@outputs('Compose')['url']"
}

Then
The 'Id' is the work Item Id that gets returned form the create a new work item step.
The 'Outputs' is from 'Compose2'. It should pop up for you on the add dynamic content popup.
Code snippet for the step above:
{
    "inputs": {
        "host": {
            "connection": {
                "name": "@parameters('$connections')['shared_visualstudioteamservices']['connectionId']"
            }
        },
        "method": "post",
        "body": {
            "Method": "PATCH",
            "Uri": "https://dev.azure.com/YourOrganization/_apis/wit/workitems/@{body('Create_a_new_work_item')?['id']}?api-version=5.0",
            "Headers": {
                "Content-Type": "application/json-patch+json"
            },
            "Body": "[\n  {\n    \"op\": \"add\",\n    \"path\": \"/relations/-\",\n    \"value\": {\n      \"rel\": \"AttachedFile\",\n      \"url\": \"@{outputs('Compose_2')}\",\n      \"attributes\": {\n        \"comment\": \"Spec for the work\"\n      }\n    }\n  }\n]",
            "IsBase64": false
        },
        "path": "/httprequest",
        "queries": {
            "account": "YourOrganization"
        },
        "authentication": "@parameters('$authentication')"
    },
    "metadata": {
        "flowSystemMetadata": {
            "swaggerOperationId": "HttpRequest"
        }
    }
}

Hope this helps!

Was this reply helpful? Yes No
TheSwilliam 40 on at

Like (2)

Report
Copy link

Link copied!
Make sure you name everything the exact same thing as what I have if you are copying and pasting from here. You will need to add in your organization name.
The schema is:

{ "type": "object", "properties": { "Id": { "type": "string" }, "Name": { "type": "string" }, "ContentBytes": { "type": "string" }, "ContentType": { "type": "string" }, "Size": { "type": "integer" } } }

Then
the binary function is:

binary(body('Parse_JSON')?['ContentBytes'])

Make sure you change the areaPath in the relative URI. I left it as mine which is just Portal.

Then
The 'Body' in 'Compose' is the body that you will get from the Http Post which I have named 'Post Attachment'
The 'url' is actually an output function:

outputs('Compose')['url']

The outputs function is getting the url property from the response json from Post Attachment.

Then
The 'Id' is the work Item Id that gets returned form the create a new work item step.
The 'Outputs' is from 'Compose2'. It should pop up for you on the add dynamic content popup.
Hope this helps!

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@TheSwilliam
Thank you for the solution. I implemented your solution and the flow did run successfully, but the file wasn't attached to the work item in Azure DevOps. Can you please advise?

Was this reply helpful? Yes No
TheSwilliam 40 on at

Like (0)

Report
Copy link

Link copied!

Hi @Anonymous,

Can you send screen shots of your two Http request actions? You have to make sure the first is a POST with the header "Content-Type": "application/octet-stream". The second one has to be a PATCH with the header "Content-Type": "application/json-patch+json"

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@TheSwilliam
Thank you for your quick response.
Please find attached the screenshots:

Was this reply helpful? Yes No
TheSwilliam 40 on at

Like (0)

Report
Copy link

Link copied!

@Anonymous everything looks good there. Do you mind sending the binary function and the compose functions. You can just send the code. Also what type of files are you sending/how big are they? You may need to change your upload type from simple to chunked. Here is the link if you'd like to read about it.
https://docs.microsoft.com/en-us/rest/api/azure/devops/wit/attachments/create?view=azure-devops-rest-6.0#start-a-chunked-upload

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@TheSwilliam

Binary Function :
binary(body('Parse_JSON')?['ContentBytes'])

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@TheSwilliam The file is a normal .txt or .pdf file

Was this reply helpful? Yes No
TheSwilliam 40 on at

Like (0)

Report
Copy link

Link copied!

@Anonymous I see your issue. You are grabbing the wrong body in your first compose. You need to grab the body that the first http request generates.

Was this reply helpful? Yes No