jira-workflow

# Jira Workflow Orchestration Skill > Complete workflow management for Jira: building stories (SAFe), getting approvals, and transitioning items through the development lifecycle (To Do → Progressing → Done). **IMPORTANT**: This project uses Next-Gen (Team-managed) Jira with custom workflow states. The actual states are: - `To Do` (backlog) - `In Review` - `Progressing` (active work) - `Out Review` - `Done` Always query available transitions first: `GET /rest/api/3/issue/{key}/transitions` ## When to Use - Creating new user stories, epics, or tasks for the project - Getting user approval before creating Jira items - Moving stories through workflow states as work progresses - Syncing Claude Code task completion with Jira status - Managing sprint planning and backlog refinement - Tracking development progress in real-time ## Prerequisites **Environment Variables:** ```bash JIRA_EMAIL=your.email@domain.com JIRA_API_TOKEN=your_api_token JIRA_BASE_URL=https://your-org.atlassian.net JIRA_PROJECT_KEY=SCRUM JIRA_BOARD_ID=1 ``` **Project Configuration:** - Must know if project is Next-Gen (Team-managed) or Classic (Company-managed) - Next-Gen: Use `parent` field for Epic links - Classic: Use `customfield_10014` for Epic links --- ## Core Workflow Pattern ### The Approval-Create-Track Loop ``` 1. PLAN: Analyze task requirements ↓ 2. PROPOSE: Present story to user for approval ↓ 3. APPROVE: User confirms or modifies ...