publish-finding-to-jira

Convert security findings into Jira issues with severity-to-priority mapping and deduplication.

6|Updated May 30, 2026

Search Tags:#security #vulnerability management #Jira #security automation #issue creation

Ready to run

npx skills add https://github.com/jassics/awesome-claude-security --skill publish-finding-to-jira

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: publish-finding-to-jira
Source: https://github.com/jassics/awesome-claude-security/tree/main/plugins/security-integrations/skills/publish-finding-to-jira
Command: npx skills add https://github.com/jassics/awesome-claude-security --skill publish-finding-to-jira

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of creating Jira issues from security findings, ensuring each finding is turned into a well-formed issue with the appropriate priority, labels, and deduplication checks.

Core Features & Use Cases

Finding to Issue Conversion: Transforms security findings into Jira issues with proper mapping of severity to priority and inclusion of remediation details.
Deduplication: Checks for existing issues to avoid duplicates.
Customizable: Allows mapping of severity to Jira priority and includes configurable issue types, projects, components, and labels.
Use Case: When you need to log a security vulnerability discovered during a pentest into Jira for tracking and remediation.

Quick Start

Create a Jira issue from a security finding by using the command: /publish-finding-to-jira: create issue "Title" "Severity" "Affected Asset" "Evidence" "Impact" "Remediation" --project "Project Name" --component "Component Name" --label "Label Name" --priority "Priority Level" --issue-type "Issue Type" --due-date "Due Date"

Frequently Asked Questions about publish-finding-to-jira

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Jira issue creation from security vulnerability findings?▼

Automating Jira issue creation from security findings involves mapping vulnerability severity to Jira priority, including remediation details, and deduplicating against existing issues. This requires an Atlassian MCP server connection and configurable project, component, and label fields.

How do I map security finding severity to Jira priority when logging vulnerabilities?▼

Mapping security finding severity to Jira priority allows customizable field configurations when creating issues. You can define the priority level explicitly using command arguments to ensure the Jira issue reflects the vulnerability's actual impact.

Can I deduplicate security vulnerabilities when creating Jira issues automatically?▼

Deduplicating security vulnerabilities when creating Jira issues checks for existing issues before logging new ones. This prevents duplicate tracking entries for the same finding, ensuring your remediation workflow remains clean and actionable.

What do I need to connect to Jira for automated security issue tracking?▼

Connecting to Jira for automated security issue tracking requires an Atlassian MCP server. This connection enables the automated creation of well-formed issues complete with evidence, impact statements, and remediation steps from your security findings.

How do I include remediation details when logging a pentest finding into Jira?▼

Including remediation details when logging a pentest finding into Jira involves passing the remediation steps as a command argument during issue creation. This ensures the resulting Jira issue contains all necessary information for developers.

Are there limitations when converting security findings into Jira issues?▼

Limitations when converting security findings into Jira issues include dependency on an active Atlassian MCP server and predefined fields for issue type, project, components, and labels. Customization is restricted to the available command arguments.