From jira
Manages Jira workflows: lists sprint and assigned issues in markdown tables, creates/updates/closes/links issues via bash scripts. Triggers on sprint/issues keywords or ACM-xxx mentions.
npx claudepluginhub yanmxa/cc-plugins --plugin jiraThis skill is limited to using the following tools:
Bundled scripts for common Jira workflows. Each operation is a single script call.
Manages Jira issues via Python CLI scripts: search, create, update, transition, comment, log work, attachments, sprints, boards, links, fields, users. Auto-triggers on Jira URLs/keys.
Manage Jira issues, boards, sprints, projects, and epics using jira-cli. Search with JQL, create, update, assign, transition, and comment from the terminal.
Manages Jira issues: view/create/update tickets, check sprints/backlogs via jira CLI, Atlassian MCP tools, or REST fallback. Activates on Jira keywords or issue keys like PROJ-123.
Share bugs, ideas, or general feedback.
Bundled scripts for common Jira workflows. Each operation is a single script call.
Scripts are at ${CLAUDE_SKILL_DIR}/scripts/.
scripts/sprint.sh [board_id]
Outputs a markdown table directly, grouped by status (New -> In Progress -> Closed) with columns: Type, Pri, Key (markdown links), Title, SP, Activity, Components, Versions, Labels. Print the output as-is. Collapse bulk CVE vulnerabilities into a summary row.
scripts/issues.sh [extra_jql_filter]
Lists all issues assigned to current user, excluding Closed and Backlog by default. Supports optional extra JQL filter (e.g. "project = ACM", "component = 'Global Hub'").
Outputs a markdown table directly, grouped by status (New -> In Progress -> Resolved) with columns: Type, Pri, Key (markdown links), Title, SP, Activity, Components, Versions. Keys prefixed with pin emoji indicate issues in the current active sprint. Print the output as-is. Collapse bulk CVE vulnerabilities into a summary row.
scripts/create.sh "<summary>" [type=Task] [priority=Major] [sp=3] [parent=ACM-xxx] [component=Global Hub] [sprint=current]
Defaults: project=ACM, component=Global Hub, assignee=current user, type=Task.
scripts/update.sh <KEY> <field=value> [field=value ...]
| Field | Example |
|---|---|
| status | status=Closed |
| sp | sp=3 |
| priority | priority=Major |
| activity | activity=Product / Portfolio Work |
| component | component=Global Hub |
| parent | parent=ACM-30822 |
| sprint | sprint=current |
| assignee | assignee=-1 (-1 = current user) |
| link | link=https://github.com/.../pull/42 |
All fields run in parallel. Custom field IDs resolved dynamically.
Activity Type values: Associate Wellness & Development, Future Sustainability, Incidents & Support, Quality / Stability / Reliability, Security & Compliance, Product / Portfolio Work
scripts/link.sh <KEY> <URL_OR_ISSUE_KEY> [custom_title]
Auto-detects URL type for title: GitHub PR -> PR #N - repo, GitLab MR -> MR !N - repo, Google Drive -> Google Drive, Blog -> Blog: slug. If target is an issue key, sets it as parent instead.
The jira-ops CLI is bundled at scripts/jira-ops. Use it for any operation not covered by the high-level scripts above.
# Issue operations
scripts/jira-ops issue get <key> [fields]
scripts/jira-ops issue search <jql> [fields] [max]
scripts/jira-ops issue create <json-payload>
scripts/jira-ops issue update <key> <json-payload>
scripts/jira-ops issue delete <key>
scripts/jira-ops issue get-field <key> <field-name>
scripts/jira-ops issue set-field <key> <field-name> <val>
scripts/jira-ops issue transition <key> <status>
scripts/jira-ops issue transitions <key>
scripts/jira-ops issue link <type> <from> <to>
scripts/jira-ops issue comment <key> <text>
scripts/jira-ops issue comment-delete <key> <comment-id>
scripts/jira-ops issue remote-link <key> <url> <title>
# Sprint / Board
scripts/jira-ops board list <project> [max]
scripts/jira-ops sprint list <board-id>
scripts/jira-ops sprint issues <sprint-id> [fields] [max]
scripts/jira-ops sprint move <sprint-id> <keys...>
# Custom field mapping
scripts/jira-ops field discover
scripts/jira-ops field search <pattern>
scripts/jira-ops field get <name>
# Global flag: --json outputs raw JSON
scripts/jira-ops --json issue get ACM-123
Source scripts/jira-ops.sh to use library functions directly. See references/api-reference.md for the full function reference (CRUD, search, transitions, ADF builders, sprint operations, URL title detection).
source "${CLAUDE_SKILL_DIR}/scripts/jira-ops.sh"
jira_search 'project = ACM AND status = Open'
ISSUE_KEY=$(jira_create_issue "$payload") || exit 1
jira_transition "$ISSUE_KEY" "In Progress"
| Variable | Required | Description |
|---|---|---|
JIRA_USER | Yes | Atlassian account email |
JIRA_API_TOKEN | Yes | API token (not password) |
JIRA_BASE_URL | Yes | e.g. https://your-domain.atlassian.net |
JIRA_AUTH_TYPE | No | basic-header (default), basic, bearer |
basic-header works through corporate proxiesadf_* builder functions in library modeparent field, not legacy custom fieldsjira-ops sprint move or jira_move_to_sprint/rest/api/3/search/jql (GET), not the deprecated POST endpointjira-ops field discover once, then use jira-ops field get "Story Points" to look up IDs