jira-issues_skill

Overview

This skill provides a lightweight Jira Cloud issues integration to create, read, update, and delete Stories, Tasks, Bugs, and Epics. It wraps Jira REST API calls and handles common field formats like Atlassian Document Format (ADF) for rich descriptions. Use it when you need programmatic issue management from Node.js or Python scripts via a shared JiraClient.

How this skill works

The skill exposes operations to POST new issues, GET issue details, PUT updates, and DELETE issues using the Jira REST API /issue endpoints. It builds request bodies with required fields (project key, issue type, summary) and converts plain descriptions into ADF structure. It also supports batching for bulk creates by executing concurrent create calls in controlled batches.

When to use it

• Create new Stories, Tasks, Bugs, or Epics programmatically from scripts or CI jobs.
• Read issue fields, status, assignee, labels, and metadata for reporting or automation.
• Update summaries, descriptions, assignees, priorities, and labels without manual UI changes.
• Delete issues or remove subtasks as part of cleanup workflows.
• Bulk-create multiple issues with batching to avoid rate limits.

Best practices

• Always supply the project.key and a valid issuetype.name supported by the target project.
• Convert descriptions to Atlassian Document Format (ADF) to preserve rich-text and avoid API errors.
• Use accountId for assignee and reporter fields — email addresses are not accepted.
• Batch bulk creates (e.g., size 10) to balance throughput and API rate limits.
• Request only needed fields with the fields query parameter to reduce payload size.

Example use cases

• Create a Story with ADF description, assign it to a user, and set priority via an automated backlog import.
• Fetch an issue by key to display summary, status, assignee, and labels in a custom dashboard.
• Update a Bug’s description and change its assignee as part of a triage automation.
• Delete obsolete test issues and optionally remove their subtasks during project cleanup.
• Bulk-create tasks from a CSV input for sprint planning scripts.