jira-bug-ticket

Create Jira bug tickets with preview and confirmation before API creation.

3|7|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/dimagi/dimagi-claude-workflows --skill jira-bug-ticket
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-bug-ticket
Source: https://github.com/dimagi/dimagi-claude-workflows/tree/main/plugins/connect-tech/skills/jira-bug-ticket
Command: npx skills add https://github.com/dimagi/dimagi-claude-workflows --skill jira-bug-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides users to file complete, consistent Jira bug tickets by collecting required and optional fields upfront, previewing the ticket for validation, and ensuring safe creation via Atlassian APIs to avoid common field errors.

Core Features & Use Cases

  • Guided collection: Prompts for a concise summary, full description, priority, impacted users/programs, product area, components, troubleshooting steps, and attachments in a single interaction.
  • Preview and confirmation: Renders a formatted ticket preview and requires explicit user confirmation before creating the issue.
  • Safe Jira integration: Locates the cloud/project, creates the issue with a markdown description, and uses a follow-up edit to add risky fields (priority, components, custom fields) only after validating them to prevent API failures.

Quick Start

Create a Jira bug ticket with summary "Login button unresponsive on mobile Safari", include steps to reproduce and expected vs actual behavior, and set priority P2.

Frequently Asked Questions about jira-bug-ticket

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

FAQPage Schema
How do I file complete Jira bug tickets in one step?

To file complete Jira bug tickets in one step, this Skill collects all required and optional fields upfront, presents a formatted preview for validation, and requires explicit confirmation before interacting with the Atlassian API to create the issue.

How does this Jira bug reporting process handle custom fields and components?

The Jira bug reporting process safely handles custom fields and components by creating the initial issue with a markdown description, then performing a follow-up edit to add these risky fields only after verifying valid field names to prevent API failures.

Can I use conversational workflows to create Jira issues with markdown descriptions?

Yes, you can use conversational workflows to create Jira issues, as the Skill guides you to describe software problems and collects summaries, impacted users, and troubleshooting steps, ultimately generating a markdown description for the Jira ticket.

What is the best way to prevent API field errors when creating Atlassian issues?

The best way to prevent API field errors when creating Atlassian issues is to validate priority, components, and custom field names in a follow-up edit after the initial issue creation, ensuring safe integration with the Atlassian API.

Do I need to specify the cloud and project before creating a Jira ticket?

Yes, you need to specify the cloud and project, as the Skill uses the Atlassian API to automatically locate your specific cloud environment and target project before attempting to create the bug issue.

What information is required for guided Jira bug ticket collection?

Guided Jira bug ticket collection requires a concise summary, full description, priority, impacted users/programs, product area, components, troubleshooting steps, and attachments, all gathered in a single interaction to ensure complete issue tracking.