jira-manager

Manage Jira Cloud issues via direct REST API calls with token authentication.

2|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill jira-manager-mbadali25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-manager
Source: https://github.com/mbadali25/useful-claude-add-ons/tree/main/skills/jira-manager
Command: npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill jira-manager-mbadali25

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, and includes scripts (resource) components.

What problem does it solve? Working with Jira tickets normally requires switching to the web UI or configuring an MCP connector. This Skill gives full read/write access to Jira Cloud directly from the terminal using the REST API v3, authenticated with just an email and API token. ## Core Features & Use Cases - Full Issue Lifecycle: Search with JQL, read, create, edit, assign, transition (close), comment on, and log work against Jira issues. - Dual Token Support: Works with both classic (unscoped) and scoped Atlassian API tokens, routing through the correct endpoint automatically. - Safe Deletion Guardrails: True issue deletion is possible but gated behind explicit confirmation, defaulting to closing via workflow transitions instead. - Use Case: Ask to "close all my resolved bugs from last sprint and log 2 hours on PROJ-123" — the Skill searches with JQL, transitions each issue through the correct workflow state, and adds the worklog entry. ## Quick Start Set JIRA_EMAIL, JIRA_API_TOKEN, and JIRA_WORKSPACE as environment variables, then ask the assistant to list your open Jira issues or create a new ticket in your project.

Frequently Asked Questions about jira-manager

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

FAQPage Schema
How do I create and update Jira issues from the command line?

Source the jira-api.sh helper, then call jira_create_issue with a project key, issue type, and summary. Follow up with jira_edit_issue passing a JSON fields object to set priority, labels, or other fields not settable at creation.

How do I close a Jira ticket via the REST API?

Status is not a plain field in Jira; you must use workflow transitions. Call jira_get_transitions to list legal transitions for the issue, then jira_transition with the transition ID. If closing fails, clear a stale resolution first with jira_clear_resolution.

Does this work with scoped Atlassian API tokens?

Yes, both classic and scoped tokens are supported. Scoped tokens require JIRA_CLOUD_ID to be set so requests route through api.atlassian.com, and the token must have read:jira-work, write:jira-work, read:jira-user, and read:me scopes.

Why does the Jira script fail with an unknown curl option error?

The helper requires curl 7.76 or newer for the --fail-with-body flag, which returns Jira's error messages on 4xx responses. Older versions shipped with RHEL 8, Ubuntu 20.04, or Debian 11 abort immediately with a clearly named error.

Can I delete a Jira issue permanently with this API?

Yes, jira_delete_issue calls the real DELETE endpoint and is irreversible, but it is gated behind explicit user confirmation. The default behavior is to transition the issue to a terminal status like Done or Cancelled instead.