Azure DevOps: Error Messages
This page lists messages that Git-Zen shows for Azure DevOps, and what to do.
When you create a work item
Section titled “When you create a work item”“Rule criteria failed; make sure all required fields and rules are being satisfied.” Azure DevOps rejected the work item. Usually a field that your process requires is missing from the form, or a value breaks a work item rule. Add the required field with Add Custom Field. Also check that the work item type exists in the project.
“The request failed with error 404; please contact support for more details” Azure DevOps could not find the project or work item type. Check the organization name and the work item types.
“The request failed with error 500; please contact support for more details” Azure DevOps or Git-Zen had an error. Try again. If it happens again, contact support.
On the Webhooks screen
Section titled “On the Webhooks screen”“You must specify your Azure DevOps organization name in the settings screen.” Enter the organization name on the Settings screen and save.
“Your Azure DevOps user account does not have admin access to a Azure DevOps project.” Git-Zen cannot see any projects. See Organization Authorization. You can also click Re-Authorize Your Token on the same screen.
“Your Azure DevOps account may not have permission to alter webhooks; please verify your account permissions.” Azure DevOps refused to add the service hooks. The OAuth user must be allowed to manage service hooks in the project. In Azure DevOps, project administrators have this permission. You can also add the service hooks manually.
“The project limit in this version is …” The Lite version limits how many projects you can select. Clear some projects, or upgrade to the Full version. See Plans and billing.
A project shows as not selected
Section titled “A project shows as not selected”Git-Zen shows a project as selected only when its “Work item updated” service hook to Git-Zen exists and is enabled. Azure DevOps can disable a service hook after repeated delivery failures. In Azure DevOps, open Project Settings > Service Hooks and check the Git-Zen subscriptions. Or select the project again in Git-Zen and save.