jira-integration

name	jira-integration
description	Create and manage Jira tickets with severity-based processing. Includes project discovery, ticket search, and branch naming.
compatibility	All repositories with Jira integration
metadata	{"version":"1.0.0","category":"workflow","tags":["jira","tickets","tracking","severity-processing"],"triggers":["on-demand"],"uses":["pr-workflow"]}

Jira Integration

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
• Workflow Overview
• Quick Reference
• References
• Severity-Based Processing
• Best Practices
• Skill Dependencies
• Related

Available Resources

📚 references/ - Detailed documentation

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

---

Workflow Overview

Step	Description	Reference
0. Discover	Find user's Jira project key	references/project-discovery.md
1. Search	Check for existing open tickets	references/ticket-search.md
2. Create	Create ticket if none exists	references/ticket-creation.md
3. Branch	Create branch with Jira key	references/branch-naming.md
4. Process	Fix by severity level	references/severity-processing.md

Quick Reference

Conventional Commit Types

All commits and tickets follow Conventional Commits format:

Type	Scope	Usage	Example
fix	security	Security vulnerabilities	fix(security): resolve critical CVE-2024-1234
fix	quality	SonarQube/code quality	fix(quality): resolve BLOCKER issues
test	<module>	Test coverage	test(payment): improve coverage
chore	deps	Dependency updates	chore(deps): update Spring Boot
docs	<area>	Documentation	docs(api): update endpoint documentation
perf	<area>	Performance	perf(queries): optimize database queries
refactor	<area>	Code restructuring	refactor(error): simplify error handling

For AI-generated commits, add attribution in the footer:

Generated with the Quality Agent by the /fix-vulnerabilities command.

Ticket Summary Format

fix(security): [SEVERITY] Dependabot vulnerabilities in [repo-name]
fix(quality): [SEVERITY] SonarQube issues in [repo-name]
test: improve coverage for [module/class]
chore(deps): update [dependency] to [version]

Branch Naming

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

Examples:

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

References

Reference	Content
references/project-discovery.md	How to discover user's Jira project key
references/ticket-search.md	JQL queries to find existing tickets
references/ticket-creation.md	Create tickets with proper format
references/branch-naming.md	Branch naming with Jira keys
references/severity-processing.md	Process by severity level

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

Skill	Purpose
pr-workflow	PR creation, commit formats, GitHub CLI

Related

• pr-workflow - PR creation and management
• stacked-prs - Stacked PR workflows