BuilderIO/issue-transitions
templates/issues/.agents/skills/issue-transitions/SKILL.md
How to change issue status in Jira. Use when transitioning issues between workflow states (e.g., To Do -> In Progress -> Done).
$ install --global
skillsauthnpx skillsauth add BuilderIO/agent-native issue-transitionsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 7:45 PM29.7s1 file scanned
SKILL.md
- name:
- issue-transitions
- description:
- >-
Issue Transitions
How Transitions Work
Jira issues move through workflow states via transitions. You can't set a status directly — you must use the available transitions for the issue's current state.
Transitioning an Issue
pnpm action transition-issue --key PROJ-123 --status "In Progress"
The script:
- Fetches available transitions for the issue (
GET /api/issues/:key/transitions) - Finds a transition matching the target status name
- Executes the transition (
POST /api/issues/:key/transitions)
Common Workflow States
| Status Category | Typical Statuses | | --------------- | ------------------------------------ | | To Do | To Do, Open, Backlog, New | | In Progress | In Progress, In Review, In QA | | Done | Done, Closed, Resolved, Released |
Status names vary by project — always use get-issue first to see the current status, then transition-issue with the desired target status.
Listing Available Transitions
The API endpoint GET /api/issues/:key/transitions returns all valid transitions from the current state. The transition-issue script handles this automatically.
Important Notes
- Status names are case-sensitive — use the exact name from the transition list
- Not all transitions are available — you can only move to states allowed by the workflow
- Some transitions require fields — certain workflows require additional fields (e.g., resolution). The script handles common cases.
After Transitioning
Always run pnpm action refresh-list after transitions to update the UI.
Related Skills
- issue-management — Full issue CRUD operations
- sprint-workflow — Sprint context for issue transitions
Related Skills
BuilderIO/booker
tools
VerifiedTrustedCommunity
Public booking flow — the state machine, animations, and URL/app-state sync.
108SKILL.mdUpdated Apr 19, 2026
BuilderIO/workflows
tools
VerifiedTrustedCommunity
Trigger-based automations — reminders, follow-ups, webhooks — across the booking lifecycle.
46SKILL.mdUpdated Apr 19, 2026
BuilderIO/team-scheduling
tools
VerifiedTrustedCommunity
Team event types, round-robin assignment, collective bookings, host weights, and no-show calibration.
46SKILL.mdUpdated Apr 19, 2026
BuilderIO/slot-engine
development
VerifiedTrustedCommunity
The pure `computeAvailableSlots` function — inputs, outputs, invariants, and debugging guide.
46SKILL.mdUpdated Apr 19, 2026