Skip to main content
skill CX Codex

Jira Automation — Claude Code skill: what it does, how to install

Automates Jira issue tracking and sprint planning. Helps configure transition workflows and calculate team capacity through chat.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add claude-office-skills/skills --skill jira-automation -a claude-code
Open on GitHub

What Jira Automation does

This skill provides workflow rules and templates for Jira projects. It defines issue states from Backlog to Done. You also get bug templates, story formats, and JQL queries for blockers.

Modifying tasks requires the project-mcp MCP server. It connects through jira_create_issue, jira_update_issue, jira_search, and jira_transition. Without that server, the agent cannot update Jira tickets directly.

The skill configures sprint schedules and WIP limits. It provides a structured foundation for Scrum ceremonies.

What it helps with

  • generate structured bug reports and user stories from templates
  • calculate team capacity and story points during sprint planning
  • find blockers and inactive tickets using curated JQL queries
  • define automated transition rules and subtask closing logic

Example prompts for the agent

  • Create a bug ticket in project DEV for login failure using the bug template
  • Plan a 14-day sprint for a team of 6 with capacity calculations
  • Find all In Progress tickets updated more than 7 days ago using JQL

How to install Jira Automation

1Skills CLI (Vercel)

npx skills add claude-office-skills/skills --skill jira-automation -a claude-code

2Manually: put the files in place

~/.claude/skills/jira-automation/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/jira-automation/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about Jira Automation

How to install Jira Automation in Claude Code?

Run npx skills add claude-office-skills/skills --skill jira-automation -a claude-code.

What does Jira Automation do?

It provides templates for Scrum artifacts, workflow automation rules, and pre-built JQL queries for tracking team progress.

What tools does Jira Automation require?

Live updates require the project-mcp server with jira_create_issue, jira_update_issue, jira_search, and jira_transition tools.

Source text

SKILL.md · MIT
---
name: Jira Automation
description: Automate Jira project management workflows, sprint planning, issue tracking, and reporting
version: 1.0.0
author: Claude Office Skills
category: project-management
tags:
  - jira
  - agile
  - sprint
  - project-management
  - automation
department: engineering
models:
  - claude-3-opus
  - claude-3-sonnet
  - gpt-4
mcp:
  server: project-mcp
  tools:
    - jira_create_issue
    - jira_update_issue
    - jira_search
    - jira_transition
capabilities:
  - Issue creation and management
  - Sprint planning automation
  - Workflow automation
  - Reporting and analytics
input:
  - Issue details
  - Sprint configurations
  - Workflow rules
  - Report parameters
output:
  - Created/updated issues
  - Sprint reports
  - Burndown charts
  - Velocity metrics
languages:
  - en
related_skills:
  - asana-automation
  - linear-automation
  - github-integration
---

# Jira Automation

Comprehensive skill for automating Jira project management and agile workflows.

## Core Workflows

### 1. Issue Management Pipeline

```
ISSUE LIFECYCLE:
┌─────────────────┐
│    Backlog      │
└────────┬────────┘
         ▼
┌─────────────────┐
│   To Do         │──────┐
└────────┬────────┘      │
         ▼               │
┌─────────────────┐      │ Blocked
│   In Progress   │◄─────┘
└────────┬────────┘
         ▼
┌─────────────────┐
│   In Review     │
└────────┬────────┘
         ▼
┌─────────────────┐
│     Done        │
└─────────────────┘
```

### 2. Automation Rules

```yaml
automation_rules:
  - name: auto_assign_on_transition
    trigger:
      type: issue_transitioned
      to_status: "In Progress"
    condition:
      assignee: unassigned
    action:
      assign_to: trigger_user

  - name: add_label_on_priority
    trigger:
      type: issue_created
      priority: highest
    action:
      - add_label: "urgent"
      - send_slack: "#dev-alerts"

  - name: auto_close_subtasks
    trigger:
      type: issue_transitioned
      to_status: "Done"
      issue_type: Story
    action:
      transition_subtasks: "Done"

  - name: sla_warning
    trigger:
      type: scheduled
      cron: "0 9 * * 1-5"
    condition:
      jql: "status = 'In Progress' AND updated < -3d"
    action:
      - add_comment: "@assignee Please update this issue"
      - send_notification: assignee
```

## Sprint Management

### Sprint Planning Template

```yaml
sprint_planning:
  name: "Sprint {{sprint_number}}"
  duration: 14  # days
  
  capacity_planning:
    team_size: 6
    hours_per_day: 6
    total_capacity: 504  # hours
    
  story_points:
    target: 42
    buffer: 10%  # for unplanned work
    
  ceremonies:
    - name: Sprint Planning
      day: 1
      duration: 2h
    - name: Daily Standup
      day: "daily"
      duration: 15m
    - name: Sprint Review
      day: 14
      duration: 1h
    - name: Retrospective
      day: 14
      duration: 1h
```

### Sprint Board Configuration

```yaml
board_config:
  type: scrum
  columns:
    - name: Backlog
      statuses: ["Backlog"]
    - name: To Do
      statuses: ["To Do", "Selected for Development"]
      wip_limit: null
    - name: In Progress
      statuses: ["In Progress"]
      wip_limit: 6
    - name: In Review
      statuses: ["Code Review", "QA"]
      wip_limit: 4
    - name: Done
      statuses: ["Done"]
      
  swimlanes:
    type: assignee
    show_epics: true
```

## Issue Templates

### Bug Report

```yaml
bug_template:
  project: DEV
  issue_type: Bug
  fields:
    summary: "[BUG] {{title}}"
    description: |
      ## Description
      {{description}}
      
      ## Steps to Reproduce
      1. {{step1}}
      2. {{step2}}
      3. {{step3}}
      
      ## Expected Behavior
      {{expected}}
      
      ## Actual Behavior
      {{actual}}
      
      ## Environment
      - Browser: {{browser}}
      - OS: {{os}}
      - Version: {{app_version}}
      
      ## Screenshots
      {{attachments}}
    
    priority: {{severity}}
    labels: ["bug", "needs-triage"]
    components: ["{{component}}"]
```

### Feature Request

```yaml
feature_template:
  project: DEV
  issue_type: Story
  fields:
    summary: "[FEATURE] {{title}}"
    description: |
      ## User Story
      As a {{user_type}}, I want to {{action}} so that {{benefit}}.
      
      ## Acceptance Criteria
      - [ ] {{criteria1}}
      - [ ] {{criteria2}}
      - [ ] {{criteria3}}
      
      ## Technical Notes
      {{tech_notes}}
      
      ## Design Mockups
      {{mockups}}
    
    labels: ["feature", "needs-refinement"]
    story_points: null  # To be estimated
```

### Epic Structure

```yaml
epic_template:
  project: DEV
  issue_type: Epic
  fields:
    summary: "{{epic_name}}"
    description: |
      ## Overview
      {{overview}}
      
      ## Goals
      - {{goal1}}
      - {{goal2}}
      
      ## Success Metrics
      | Metric | Current | Target |
      |--------|---------|--------|
      | {{metric1}} | {{current1}} | {{target1}} |
      
      ## Timeline
      Start: {{start_date}}
      Target Completion: {{end_date}}
      
      ## Dependencies
      {{dependencies}}
      
    child_issues:
      - type: Story
        count: "auto"
```

## JQL Queries Library

### Common Queries

```jql
# My open issues
assignee = currentUser() AND resolution = Unresolved ORDER BY priority DESC

# Sprint progress
project = DEV AND Sprint = "Sprint 15" ORDER BY status

# Bugs by severity
project = DEV AND type = Bug AND resolution = Unresolved 
ORDER BY priority DESC, created ASC

# Stale issues
project = DEV AND status = "In Progress" AND updated < -7d

# Ready for review
project = DEV AND status = "Code Review" AND "Code Reviewer" is EMPTY

# Release scope
fixVersion = "v2.5.0" AND resolution = Unresolved

# Team velocity
project = DEV AND type = Story AND Sprint in closedSprints() 
AND resolved >= -90d

# Blockers
project = DEV AND (priority = Blocker OR labels = blocked)
AND resolution = Unresolved
```

## Reporting & Dashboards

### Sprint Dashboard

```
SPRINT 15 DASHBOARD
═══════════════════════════════════════

Progress:
Day 8 of 14 │ ████████░░░░░░ 57%

Story Points:
Committed: 42
Completed: 24  │ ████████████░░░░░░░░ 57%
Remaining: 18

Burndown:
│ 42 ┤ ▪
│    │  ▪▪
│    │    ▪▪
│    │      ▪▪▪
│ 21 ┤         ▪ ← Ideal
│    │          ▪▪
│    │            ▪▪
│    │              ▪▪
│  0 ┤                ▪
└────┴────────────────────
     Day 1           Day 14

Issue Status:
To Do        ███░░░░░░░ 6
In Progress  █████░░░░░ 8
In Review    ████░░░░░░ 5
Done         █████████░ 12
```

### Velocity Chart

```
TEAM VELOCITY (Last 6 Sprints)
═══════════════════════════════════════

│  50 ┤
│     │           ▓▓
│  40 ┤    ▓▓     ▓▓     ▓▓     ▓▓
│     │    ▓▓ ▓▓  ▓▓     ▓▓ ▓▓  ▓▓
│  30 ┤ ▓▓ ▓▓ ▓▓  ▓▓ ▓▓  ▓▓ ▓▓  ▓▓
│     │ ▓▓ ▓▓ ▓▓  ▓▓ ▓▓  ▓▓ ▓▓  ▓▓
│  20 ┤ ▓▓ ▓▓ ▓▓  ▓▓ ▓▓  ▓▓ ▓▓  ▓▓
│     │ ▓▓ ▓▓ ▓▓  ▓▓ ▓▓  ▓▓ ▓▓  ▓▓
│  10 ┤ ▓▓ ▓▓ ▓▓  ▓▓ ▓▓  ▓▓ ▓▓  ▓▓
│     │ ▓▓ ▓▓ ▓▓  ▓▓ ▓▓  ▓▓ ▓▓  ▓▓
│   0 ┴─────────────────────────────
       S10 S11 S12 S13 S14 S15

Average: 38 points | Trend: +5%
```

## Integration Workflows

### GitHub Integration

```yaml
github_integration:
  branch_creation:
    trigger: issue_transitioned_to_in_progress
    pattern: "{{issue_type}}/{{issue_key}}-{{summary_slug}}"
    
  commit_linking:
    patterns:
      - "{{issue_key}}"
      - "#{{issue_key}}"
    action: add_comment_with_link
    
  pr_automation:
    on_pr_open:
      - transition_issue: "Code Review"
      - add_pr_link_to_issue
    on_pr_merge:
      - transition_issue: "Done"
      - add_comment: "Merged in {{pr_url}}"
```

### Slack Integration

```yaml
slack_integration:
  channels:
    dev_updates: "#dev-updates"
    alerts: "#dev-alerts"
    
  notifications:
    - event: blocker_created
      channel: alerts
      message: "🚨 Blocker: {{issue.key}} - {{issue.summary}}"
      
    - event: sprint_started
      channel: dev_updates
      message: "🏃 Sprint {{sprint.name}} has started! Goal: {{sprint.goal}}"
      
    - event: release_completed
      channel: dev_updates
      message: "🚀 Release {{version}} is live!"
```

## Workflow Customization

### Custom Workflow

```yaml
workflow:
  name: Development Workflow
  statuses:
    - Backlog
    - Ready for Dev
    - In Progress
    - Code Review
    - QA
    - Ready for Release
    - Done
    
  transitions:
    - from: Backlog
      to: Ready for Dev
      name: "Refine"
      conditions:
        - story_points_set
        
    - from: Ready for Dev
      to: In Progress
      name: "Start Work"
      post_functions:
        - assign_to_current_user
        
    - from: In Progress
      to: Code Review
      name: "Submit for Review"
      validators:
        - has_linked_pr
        
    - from: Code Review
      to: QA
      name: "Pass Review"
      conditions:
        - all_reviewers_approved
        
    - from: QA
      to: Done
      name: "Pass QA"
      post_functions:
        - resolve_issue
```

## Best Practices

1. **Keep Issues Small**: Break down to complete in 1-2 days
2. **Write Clear Descriptions**: Include all context needed
3. **Link Related Issues**: Use proper issue linking
4. **Update Status Regularly**: Move cards as work progresses
5. **Use Labels Consistently**: Establish team conventions
6. **Estimate in Points**: Use relative sizing
7. **Review Backlog Weekly**: Keep backlog groomed

© Claude Office Skills · MIT · claude-office-skills/skills

Similar skills

Everything for Notes, tasks and projects →

From the same set109

PDF Form Filler This skill fills PDF forms from your data and pulls field values back out of completed documents. Useful when forms pile up or repeat. CX Codex +1 4,700installs Expense Tracker Extracts receipt data, checks company spending policies, and prepares reimbursement reports. Useful for corporate expense workflows. CX Codex +1 4,700installs customer-success A skill for managing customer accounts: onboarding, health scoring, QBRs, expansion and retention playbooks. Useful if you run a SaaS book of business. CX Codex +1 4,700installs crypto-report Breaks down a crypto project's tokenomics, on-chain metrics and competitors, then writes the findings into a markdown report. Handy when you need the full picture on a token fast. CX Codex +1 4,700installs ETL Pipeline A skill for designing and automating ETL pipelines: pull from databases and APIs, transform, load into warehouses. Useful when you need a recurring data flow. CX Codex +1 4,800installs devops-automation A skill that lays out DevOps workflows: CI/CD pipelines, alert routing, incident response and server provisioning. Useful when you need deploy and on-call steps written down. CX Codex +1 4,800installs Monday.com Automation A skill that automates Monday.com from your agent: creates and updates items, configures boards, automation recipes and dashboards. CX Codex +1 4,600installs Content Research Writer Researches topics, gathers supporting data, and drafts long-form articles or blog posts. Useful for marketing teams producing structured content. CX Codex +1 4,700installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor