スキル一覧に戻る
JoshuaRamirez

work-item-fields

by JoshuaRamirez

Azure DevOps plugin for Claude Code - uses Azure CLI (az) instead of buggy MS MCP server

0🍴 0📅 2025年12月27日
GitHubで見るManusで実行

SKILL.md


Azure DevOps Work Item Fields Reference (Verified)

System Fields (All Work Item Types)

Display NameReference NameTypeDescription
IDSystem.IdIntegerUnique identifier
TitleSystem.TitleStringWork item title
StateSystem.StateStringCurrent state
ReasonSystem.ReasonStringReason for state
Work Item TypeSystem.WorkItemTypeStringBug, Task, etc.
Assigned ToSystem.AssignedToIdentityPerson assigned
Created BySystem.CreatedByIdentityCreator
Created DateSystem.CreatedDateDateTimeCreation timestamp
Changed BySystem.ChangedByIdentityLast modifier
Changed DateSystem.ChangedDateDateTimeLast modified
Area PathSystem.AreaPathTreePathArea classification
Iteration PathSystem.IterationPathTreePathSprint/iteration
TagsSystem.TagsStringSemicolon-separated
DescriptionSystem.DescriptionHTMLRich text description
HistorySystem.HistoryHTMLDiscussion entry
RevSystem.RevIntegerRevision number
Board ColumnSystem.BoardColumnStringKanban column
Board LaneSystem.BoardLaneStringSwimlane

Common Fields by Category

Scheduling

Display NameReference NameType
Story PointsMicrosoft.VSTS.Scheduling.StoryPointsDouble
EffortMicrosoft.VSTS.Scheduling.EffortDouble
Original EstimateMicrosoft.VSTS.Scheduling.OriginalEstimateDouble
Remaining WorkMicrosoft.VSTS.Scheduling.RemainingWorkDouble
Completed WorkMicrosoft.VSTS.Scheduling.CompletedWorkDouble
Start DateMicrosoft.VSTS.Scheduling.StartDateDateTime
Finish DateMicrosoft.VSTS.Scheduling.FinishDateDateTime

Priority & Severity

Display NameReference NameValues
PriorityMicrosoft.VSTS.Common.Priority1, 2, 3, 4
SeverityMicrosoft.VSTS.Common.Severity1 - Critical, 2 - High, 3 - Medium, 4 - Low
Value AreaMicrosoft.VSTS.Common.ValueAreaBusiness, Architectural
RiskMicrosoft.VSTS.Common.Risk1 - High, 2 - Medium, 3 - Low

Bug-Specific

Display NameReference NameType
Repro StepsMicrosoft.VSTS.TCM.ReproStepsHTML
System InfoMicrosoft.VSTS.TCM.SystemInfoHTML
Found InMicrosoft.VSTS.Build.FoundInString
Integration BuildMicrosoft.VSTS.Build.IntegrationBuildString
Display NameReference NameUsage
ChildSystem.LinkTypes.Hierarchy-ForwardworkItemLink
ParentSystem.LinkTypes.Hierarchy-ReverseworkItemLink
SuccessorSystem.LinkTypes.Dependency-ForwardworkItemLink
PredecessorSystem.LinkTypes.Dependency-ReverseworkItemLink
RelatedSystem.LinkTypes.RelatedworkItemLink
DuplicateSystem.LinkTypes.Duplicate-ForwardworkItemLink
Duplicate OfSystem.LinkTypes.Duplicate-ReverseworkItemLink
Tested ByMicrosoft.VSTS.Common.TestedBy-ForwardworkItemLink
TestsMicrosoft.VSTS.Common.TestedBy-ReverseworkItemLink
AffectsMicrosoft.VSTS.Common.Affects-ForwardworkItemLink
Affected ByMicrosoft.VSTS.Common.Affects-ReverseworkItemLink
Referenced ByMicrosoft.VSTS.TestCase.SharedParameterReferencedBy-ForwardworkItemLink
ReferencesMicrosoft.VSTS.TestCase.SharedParameterReferencedBy-ReverseworkItemLink
Test CaseMicrosoft.VSTS.TestCase.SharedStepReferencedBy-ForwardworkItemLink
Shared StepsMicrosoft.VSTS.TestCase.SharedStepReferencedBy-ReverseworkItemLink

List all relation types

az boards work-item relation list-type -o table

Show work item with relations

az boards work-item relation show --id 123 -o json

Add parent-child relationship

# Add child link (work item 123 becomes parent of 456)
az boards work-item relation add --id 123 --relation-type "Child" --target-id 456 -o json

# Add parent link (work item 123 becomes child of 789)
az boards work-item relation add --id 123 --relation-type "Parent" --target-id 789 -o json

# Add related link
az boards work-item relation add --id 123 --relation-type "Related" --target-id 456 -o json

Note: Friendly Names vs Reference Names

The CLI uses friendly names (from the "Name" column), not reference names:

  • Use "Parent" not "System.LinkTypes.Hierarchy-Reverse"
  • Use "Child" not "System.LinkTypes.Hierarchy-Forward"
  • Use "Related" not "System.LinkTypes.Related"

Tip: Run az boards work-item relation list-type -o table to see all available friendly names in the "Name" column.

Create with fields

az boards work-item create \
  --type "Bug" \
  --title "Login fails" \
  --fields "Microsoft.VSTS.Common.Priority=1" \
           "Microsoft.VSTS.Common.Severity=2 - High" \
           "System.Tags=urgent;login" \
  -o json

Update fields

az boards work-item update \
  --id 123 \
  --state "In Progress" \
  --assigned-to "user@example.com" \
  --fields "Microsoft.VSTS.Scheduling.RemainingWork=4" \
  -o json

Add comment (discussion)

az boards work-item update --id 123 --discussion "This is my comment" -o json

List All Fields in Project

az boards work-item list-fields -o table

Field Gotchas

  1. Identity fields: Use email or display name, not GUID
  2. HTML fields: Wrap in HTML tags: <p>Description</p>
  3. TreePath fields: Use backslash: Project\Area\SubArea
  4. Tags: Semicolon-separated in API, comma-separated in CLI
  5. DateTime: ISO 8601 format: 2024-01-15T10:30:00Z
  6. Double fields: Use decimal: 4.5 not 4,5
  7. State values: Must match exactly including case - check your process template

スコア

総合スコア

55/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

0/5
タグ

1つ以上のタグが設定されている

0/5

レビュー

💬

レビュー機能は近日公開予定です