Create work item associate with build results in "Build link cannot be read" error

[ossentoo]

• CreateWorkItem task
• Azure DevOps
• Agent type. I have tried with both our Azure hostsed agents and default windows-latest hosts
• yaml pipeline

I want to create a work item after each release. However, unfortunately i don't get a link back to the original build

Adding the following yaml for the task results in a build link not being created:

• task: CreateWorkItem@1 displayName: Create work item inputs: teamProject: 'Our-Releases' workItemType: 'User Story' title: '$(System.TeamProject) $(Build.DefinitionName) $(System.StageDisplayName) $(Build.BuildNumber)' assignedTo: '$(Build.RequestedForId)' areaPath: 'Our-Releases' iterationPath: 'Our-Releases' fieldMappings: 'State=Resolved' associate: true

Instead I get an error where the link should be displayed:

Build link could not be read

Task logs Run your pipeline with the following variables:

• For BuildQualityChecks: System.Debug and BQC.LogRawData set to true
• For CreateWorkItem: System.Debug set to true
• For PostBuildCleanup: System.Debug and PBC.LogRawData set to true

Send the task log to PSGerExtSupport@microsoft.com and reference your GitHub issue.

Attention: The log file may contain sensitive data (e.g., server or organization names, project names, variable information). Please do not attach the log to your GitHub issue and or remove the information from the log file before attaching or sending.

[ReneSchumacher]

Hi @ossentoo,

I have tried to reproduce this issue in our testing environment without success. Is this a persistent issue? Could you maybe open the following URI in the browser (replace the placeholders with the correct values) and send the resulting JSON to PSGerExtSupport@Microsoft.com so we can take a look:

https://dev.azure.com/{your org}/{your project}/_apis/wit/workitems/{id of work item with error}?$expand=all

[ReneSchumacher]

Hi again,

I'm closing this issue now as we cannot reproduce it and did not receive additional feedback.

[ossentoo]

this issue has resolved itself without me doing anything! thanks anyway