When any user tries to select role as “Service account” this error message is displayed. This error message is displayed when there are no service… Read More »500: Role name Service account doesn’t not exist in the current scope
Issue: You may see a message like this shown below when you kept the workitem longer than usual The below message is usually seen when… Read More »History details is outdated. Please save your changes, revert them, or refresh to see the latest details – Azure DevOps
Issue : Whenever you tag a particular person in the User Story or Bug or Epic or anyworkitem you may get an error as shown… Read More »User XXXX cannot be mentioned in Bug/Epic/Feature/Task/UserStory
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… Read More »The identity value for the field ‘Assigned To’ is an unknown identity
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… Read More »VS402358: There is an existing process template with name Scrum.
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’… Read More »VS402378: You’ve specified an invalid process name.
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… Read More »VS403463: The conditional access policy defined by your Azure Active Directory administrator has failed.
This error usually occurs when you are trying to access an Azure DevOps Project or an Azure DevOps url and this is mainly due to… Read More »TF400813: User is not authorized to access this resource
This is mainly due to folder deletion issue as you cna see it from here..This can be fixed by changing the task version to 2… Read More »Unhandled: EPERM: operation not permitted, open ‘E:\_Agent\_work\.taskkey’