Does the CLI use field reference names or friendly names?

The Azure CLI (az boards) typically uses friendly names for relation types (like 'Parent' or 'Child') while requiring specific reference names for field-level updates.

What is the correct format for identity fields like 'Assigned To'?

Identity fields in Azure DevOps should use the user's email address or display name rather than a unique GUID.

Can I see all fields available in my specific project?

Yes, you can run 'az boards work-item list-fields -o table' to see a complete list of fields including custom ones for your project.

How do I add a comment to an Azure DevOps work item using this skill?

You can use the 'az boards work-item update' command with the '--discussion' flag followed by your comment text.

Azure DevOps Work Item Fields Reference

Name: Azure DevOps Work Item Fields Reference
Author: JoshuaRamirez

byJoshuaRamirez

Collaboration Tools

Provides a comprehensive reference for Azure DevOps work item fields, link types, and CLI commands to streamline project management tasks.

About

This skill serves as an authoritative guide for Claude Code users interacting with Azure DevOps (ADO). It offers precise mapping of system fields, scheduling attributes, and bug-specific metadata, alongside verified Azure CLI (az boards) command patterns. By bridging the gap between human-readable field names and their technical reference names, it enables developers to efficiently create, update, and link work items directly through their AI assistant without leaving the terminal.

Key Features

0 GitHub stars
Comprehensive mapping of System, Scheduling, and Priority fields
Detailed formatting guidance for Identity, HTML, and TreePath fields
Verified link types and relation syntax for Parent-Child hierarchies
Reference for bug-specific fields like Repro Steps and System Info
Ready-to-use Azure CLI (az boards) command snippets for field updates

Use Cases

Automating the creation of complex bugs with specific priority and severity metadata
Establishing relationships between work items such as linking tasks to parent stories
Updating project management metrics like Story Points and Remaining Work via CLI

About

Key Features

0 GitHub stars
Comprehensive mapping of System, Scheduling, and Priority fields
Detailed formatting guidance for Identity, HTML, and TreePath fields
Verified link types and relation syntax for Parent-Child hierarchies
Reference for bug-specific fields like Repro Steps and System Info
Ready-to-use Azure CLI (az boards) command snippets for field updates

Use Cases

Automating the creation of complex bugs with specific priority and severity metadata
Establishing relationships between work items such as linking tasks to parent stories
Updating project management metrics like Story Points and Remaining Work via CLI