jira-to-issue

Name: jira-to-issue
Availability: InStock
Author: iimuz

Convert JIRA bugs into GitHub Issues using a Markdown template.

3|1|Updated Aug 22, 2015

Search Tags:#automation #workflow #template #github #migration #jira #issue

Ready to run

npx skills add https://github.com/iimuz/dotfiles --skill jira-to-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jira-to-issue
Source: https://github.com/iimuz/dotfiles/tree/main/.config/copilot/skills/jira-to-issue
Command: npx skills add https://github.com/iimuz/dotfiles --skill jira-to-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automatically converts JIRA bug tickets into GitHub Issues by extracting ticket details and applying a standardized Markdown template with proper labeling.

Core Features & Use Cases

Read JIRA ticket details (ID, summary, description, steps, attachments) and map them into a GitHub Issue.
Apply the template defined at references/issue_template.md to ensure consistency and readability.
Create a GitHub Issue in a target repository with the sqa-report label to facilitate downstream review (with optional steps to customize labels as needed).

Quick Start

Provide a JIRA ticket URL and target GitHub repository to generate a formatted GitHub Issue.

Frequently Asked Questions about jira-to-issue

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

FAQPage Schema

How do I convert JIRA bugs to GitHub Issues automatically?▼

To convert JIRA bugs to GitHub Issues, provide a JIRA ticket URL and target repository. This skill extracts ticket details like IDs and descriptions, then applies a standardized Markdown template to generate well-structured GitHub Issues.

Can I migrate JIRA ticket attachments and labels to a GitHub Issue?▼

Yes, you can migrate JIRA ticket attachments and labels to a GitHub Issue. The conversion process preserves ticket IDs, summaries, descriptions, details, attachments, and labels, ensuring comprehensive data transfer across repositories.

Does migrating JIRA bugs to GitHub Issues require a specific issue template?▼

Migrating JIRA bugs to GitHub Issues uses a specific Markdown template located at references/issue_template.md. This enforces consistent formatting and readability, while automatically applying the sqa-report label for downstream review.

What is the best way to bulk convert JIRA tickets to GitHub Issues?▼

The best way to bulk convert JIRA tickets to GitHub Issues is using an automation workflow that extracts ticket details and maps them into a standardized template. This supports bulk conversions across repositories while preserving labels and attachments.

How do I customize labels when migrating JIRA bugs to GitHub Issues?▼

When migrating JIRA bugs to GitHub Issues, the process enforces the sqa-report label by default for downstream consistency. You can customize labels as needed through optional steps during the repository issue creation process.

Do I need access to both JIRA and GitHub to migrate issue details?▼

Yes, you need access to both JIRA and GitHub to migrate issue details. The workflow requires reading source ticket details from JIRA and creating the newly formatted issues in the target GitHub repository.