0
votes

We are using logic apps to automatically create Azure Devops work items. But I frequently get issues related to identity if that identity does not already have an existing item assigned to them. Currently, I raise an email alert on this error and I can always create an item manually in ADO and retrigger the logic app. Why does this happen? Is there a fallback that I can use?

For eg. If [email protected] has never been assigned an item in the ADO and I try to create a work item from the logic app using the Azure Devops connector, it sometimes fails giving error The identity value '[email protected]' for field 'Assigned To' is an unknown identity.

Please note that manual assignment works.

1
Is there any update for this issue? Feel free to let me know if my answer could give you some help. Just a reminder of this. - Kevin Lu-MSFT
Thanks @KevinLu-MSFT, I will try and update you on how this goes - Ashutosh
HI @Ashutosh. To follou up. Could you please check if the answer could solve this issue? If you have any update, feel free to let me know. - Kevin Lu-MSFT
Sure @KevinLu-MSFT, will update you as soon as I try this - Ashutosh

1 Answers

0
votes

The identity value '[email protected]' for field 'Assigned To' is an unknown identity.

It seems that the account identity couldn't be recognized. Based on my test, I could reproduce this issue.

To solve this issue, you could try to set the assign to field as username<useraccount> format in Logic app design. For example: test

enter image description here

In this case, even if the user is not assigned a work item, the account address can still be identified.

Hope this helps.