jira-issue-management

Automate JIRA issue CRUD operations across projects via REST API v3.

42|8|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/grandcamel/JIRA-Assistant-Skills --skill jira-issue-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-issue-management
Source: https://github.com/grandcamel/JIRA-Assistant-Skills/tree/main/skills/jira-issue
Command: npx skills add https://github.com/grandcamel/JIRA-Assistant-Skills --skill jira-issue-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill centralizes JIRA issue management by providing a single interface to create, read, update, and delete issues across projects, reducing context switching and manual overhead.

Core Features & Use Cases

  • Create issues (Bug, Task, Story) with pre-filled templates and fields
  • Retrieve complete issue details, status, and history
  • Update fields (priority, assignee, labels, links) and delete issues when needed
  • Supports Agile fields, relationships, time tracking, and REST API v3 interactions
  • Access to internal references and asset templates to guide usage

Quick Start

Example: Create a Bug in PROJ and view it with: jira-as issue create --project PROJ --type Bug --summary "Login fails on mobile" && jira-as issue get PROJ-123

Frequently Asked Questions about jira-issue-management

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

FAQPage Schema
How do I automate JIRA issue creation and updates across multiple projects?

You can automate JIRA issue creation and updates across projects by using the Jira REST API v3 to execute CRUD operations, pre-fill fields with templates, and manage issue details programmatically.

What's the best way to retrieve JIRA issue details and history using the REST API?

The best way to retrieve JIRA issue details and history is to use a centralized interface that queries the Jira REST API v3, allowing you to pull complete status updates, field changes, and relationship links.

Do I need JIRA Cloud credentials to manage issues via the REST API v3?

Yes, you need JIRA Cloud credentials and REST API v3 access to authenticate and perform issue lifecycle operations like creating bugs, updating assignees, or deleting stories.

Can I use templates to create bugs, tasks, and stories in JIRA?

Yes, you can use internal templates and references to create bugs, tasks, and stories in JIRA, automatically pre-filling fields like priority, labels, and time tracking details.

How do I update Agile fields and time tracking for JIRA issues?

To update Agile fields and time tracking for JIRA issues, you send field updates through the Jira REST API v3, modifying attributes like assignee, priority, labels, and issue relationships.

Are there limitations to deleting JIRA issues through an automated CLI?

Deleting JIRA issues through an automated CLI is supported, but it requires proper JIRA Cloud credentials and REST API v3 access, and should be used carefully to avoid unintended data loss.