---

name: jira-workflow description: Jira ticket creation and management for AI agent commands, with severity-based processing and proper integration version: 1.0.0 compatibility: All repositories with Jira integration

metadata: category: workflow tags: - jira - tickets - tracking - severity-processing triggers: - on-demand uses: - pr-lifecycle

Jira Workflow

Best practices for AI agents to create and manage Jira tickets when performing automated work like fixing vulnerabilities, resolving SonarQube issues, or improving test coverage.

Core Principles

1. Create Ticket Before Work - Always create/find a Jira ticket before starting
2. Discover Project Key - Never hardcode project keys
3. Search Before Creating - Check for existing tickets first
4. Severity-Based Processing - Process issues one severity level at a time
5. Link Everything - Connect Jira → Branch → Commits → PR

Skill Contents

Sections

• Core Principles (L24-L31)
• Workflow Overview (L56-L65)
• Quick Reference (L66-L100)
• References (L101-L110)
• Severity-Based Processing (L111-L127)
• Best Practices (L128-L135)
• Skill Dependencies (L136-L141)
• Related (L142-L145)

Available Resources

📚 references/ - Detailed documentation

• branch naming
• project discovery
• severity processing
• ticket creation
• ticket search

---

Workflow Overview

Quick Reference

Emoji Conventions

Ticket Summary Format

Copy🤖🛡️ Fix [SEVERITY] Dependabot vulnerabilities in [repo-name]
🤖✅ Resolve [SEVERITY] SonarQube issues in [repo-name]
🤖🧪 Improve test coverage for [module/class]
🤖📦 Update [dependency] to [version]

Branch Naming

Copy{type}/{JIRA-KEY}-{short-description}

Examples:

• fix/PROJ-123-critical-vulnerabilities
• fix/PROJ-456-blocker-sonar-issues
• test/PROJ-789-coverage-payment-service

References

Severity-Based Processing

Vulnerability Severity Order

1. CRITICAL - Fix first
2. HIGH - Only after no CRITICAL remain
3. MEDIUM/MODERATE - Only after no HIGH remain
4. LOW - Only after no MEDIUM remain

SonarQube Severity Order

1. BLOCKER - Fix first
2. CRITICAL - Only after no BLOCKER remain
3. MAJOR - Only after no CRITICAL remain
4. MINOR - Only after no MAJOR remain
5. INFO - Only after no MINOR remain

Best Practices

1. One severity per PR - Keep PRs focused and reviewable
2. Batch related fixes - Group similar issues in one commit
3. Clear descriptions - Document what was fixed and why
4. Link everything - Jira ticket ↔ Branch ↔ Commits ↔ PR
5. Update ticket status - Move ticket through workflow as work progresses

Skill Dependencies

Related

• .claude/skills/pr-lifecycle - PR creation and management
• .claude/skills/stacked-prs - Stacked PR workflows