User XXXX cannot be mentioned in Bug/Epic/Feature/Task/UserStory
Issue : Whenever you tag a particular person in the User Story or Bug or Epic or anyworkitem you may get an error as shown below stating that user ‘XXXXX’ cannot be mentioned in...
Category: AzureDevOps Issues
The identity value for the field ‘Assigned To’ is an unknown identity
Issue: When you assign a particular person to this workitem, Issues like this might occur. This error occurs due to the fact, that the user who have put in Assigned To is not identifable...
The field ‘State’ contains the value ‘XXXX’ that is not in the list of supported values – AzureDevOps
Issue: You might have seen this error when you are trying to update a old workitem and this specifically occurs when you have opened a workitem Solution : You may need to change the...
VS402358: There is an existing process template with name Scrum.
This issue occurs when there are 2 process templates with the same name.So you may need to rename one of the process template Solution: Rename the process template to another name and try it...
VS402378: You’ve specified an invalid process name.
This error occurs when you specify an invalid process name Issue: You’ve specified an invalid process name.Process names can’t be empty or greater than ‘256’ characters, and can’t contain the following characters ‘,;’~:/*|?”&%$!+=()[]{}<>’. Solution:...
VS403463: The conditional access policy defined by your Azure Active Directory administrator has failed.
This error occurs in Azure DevOps when the user is outside of the network domain. This is because the conditional access policy has been set to “true” for the Azure DevOps organization. Issue: VS403463:...
TF401232: WorkItem XXX doesn’t exist – Azure DevOps
You may have often seen this issue, whenever you are trying to access a workitem. This may be due to 2 reasons You may not have access or permissions to read the workitem WorkItem...
Failed to create Release artifact directory – Azure DevOps Issue
Sometimes you may get an issue like this shown below This issue occurs because the Release Artifact directory is opened in some other window or being used by another application
MSBuild is not recognized as an internal or external command – Fortify SCA – Azure DevOps
Issue/Error: MSBuild is not recognized as an internal or external command, operable program or batch file. Compiler Execution failed (exit code: 1) Compiler Output: Sometimes you may have faced an issue like the above...
Copy Files task – The specified Network password is not correct |AzureDevOps
Issue: Failed to Create PSDrive with Destination:”\\xxxxx\xxxx\” .The specified network password is not correct This issue mainly occurs due to either password or username being not correct. Follow the solution displayed below to get...
