From connect-tech
Create Jira bug tickets with all required and optional fields. Use this skill whenever a user wants to file, log, report, or create a bug, defect, or issue in Jira. Triggers on phrases like "create a bug ticket", "log a bug", "file a Jira issue", "report a bug", "open a ticket for this bug", or any time someone describes a software problem and wants it tracked. Always use this skill when bug reporting or Jira ticket creation is involved, even if the user doesn't say "skill" or "Jira" explicitly.
npx claudepluginhub dimagi/dimagi-claude-workflows --plugin connect-techThis skill uses the workspace's default tool permissions.
Guide the user through filing a complete, well-structured Jira bug ticket. Collect all required and optional fields upfront in one shot, show a formatted preview, and only create the ticket after explicit user confirmation.
Creates new Jira issues via explicit /create-jira-issue invocation. Supports project key, issue type, summary, Markdown body, assignee, priority, labels, components, parent, custom fields; previews payload, requires confirmation before POSTing.
Triages bug reports and error messages by searching Jira for duplicates, checking fix history, and creating structured issues or adding comments.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Share bugs, ideas, or general feedback.
Guide the user through filing a complete, well-structured Jira bug ticket. Collect all required and optional fields upfront in one shot, show a formatted preview, and only create the ticket after explicit user confirmation.
Ask the user for everything in a single message. Use this template:
Let's file a bug ticket! Please provide the following:
Required:
Optional (leave blank to skip):
Once the user provides info, display a clean preview of the ticket before creating it:
📋 JIRA BUG TICKET PREVIEW
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Type: Bug
Summary: [summary]
Priority: [P0/P1/P2/P3]
Description:
[description]
── Optional Fields ──────────────────────
Users/Programs Impacted: [value or —]
Product Area / Feature: [value or —]
Program Impacted: [value or —]
Components: [value or —]
Troubleshooting Taken: [value or —]
Attachments: [value or —]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Then ask: "Does this look correct? Reply 'yes' to create the ticket, or let me know what to change."
Before creating, you need the Jira cloudId and the right project. Use the Atlassian tools:
getAccessibleAtlassianResources to get the cloudId.CI — use it without asking unless the user has explicitly specified a different project or says they want to choose.Use createJiraIssue with:
issueTypeName: "Bug"summary: the summarycontentFormat: "markdown" — always set this so the description renders correctlydescription: Build a well-structured description in Markdown that includes:
additional_fields — Known PitfallsThe additional_fields parameter passes fields directly to the Jira API. Several fields commonly fail:
priority: The priority names must match the project's configured priorities EXACTLY. The names vary by project — "Medium", "Highest", etc. may not exist. Do NOT include priority in the first attempt. If the user specified a priority, try adding it in a follow-up editJiraIssue call, or first call getJiraIssueTypeMetaWithFields to discover the valid priority names for the project.components: Components must already exist in the project. Jira returns a permissions error ("You do not have permission to create new components") if you reference a component name that doesn't exist — it tries to create it rather than failing gracefully. Do NOT include components unless you have verified they exist via getJiraIssueTypeMetaWithFields.customfield_*: Custom field IDs vary by Jira instance. Discover them via getJiraIssueTypeMetaWithFields before using.Recommended approach: Create the ticket with only summary, description, issueTypeName, and contentFormat first. If that succeeds, use editJiraIssue to add priority, components, and other optional fields in a second call. This avoids a single bad field blocking ticket creation entirely.
## Bug Description
[user's description]
## Steps to Reproduce
[extract from description if present, otherwise omit]
## Expected vs Actual Behavior
[extract from description if present, otherwise omit]
---
**Product Area / Feature:** [value or N/A]
**Program Impacted:** [value or N/A]
**Users / Programs Impacted:** [value or N/A]
## Troubleshooting Steps Taken
[value or N/A]
## Attachments
[value or N/A]
After creating, respond with:
PROJ-123)