bug-tracker-workflow

Overview

Every mainstream tracker exposes the same four core operations - create, transition, search, and update/comment - behind a different API shape. This skill runs the bug workflow tracker-agnostically, with Jira Cloud REST API v3 worked in full below and per-platform deep dives in references:

Tracker	API shape	Lifecycle model	Deep dive
Jira Cloud	REST v3, ADF rich text	Configurable workflow engine; look up transition IDs at runtime	Worked below + references/jira.md
Linear	GraphQL only	Per-team `WorkflowState` objects; resolve by `type`, not display name	references/linear.md
GitHub Issues	REST + Projects v2 GraphQL	Two states (open/closed) + `state_reason`; severity/priority via labels	references/github-issues.md
Azure DevOps	WIT REST 7.1, JSON Patch	Process-template states (Agile: New/Active/Resolved/Closed); WIQL search	references/azuredevops.md

The tracker-agnostic rules that hold on all four platforms: