Stats
Actions
Tags
From jira
Updates existing Jira issues using jirac CLI, including summary, description, assignee, priority, labels, components, fix versions, and custom fields. Checks installation and maps requests to flags.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jira:update-issueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Update a Jira issue using `jirac`.
Update a Jira issue using jirac.
Steps:
jirac is available by running jirac --version. If it is missing, tell the user to install it with cargo install jira-commands.--summary--assignee--priority--labels--components--fix-version--description-file--field customfield_XXXXX=valuejirac issue update <ISSUE-KEY> ... with only the requested fields.jirac issue fields -p <PROJECT> --issue-type '<TYPE>' first.Examples:
jirac issue update PROJ-123 --summary 'fix OAuth callback'jirac issue update PROJ-123 --priority High --assignee menpx claudepluginhub mulhamna/jira-commands --plugin jiraUpdates an existing Jira issue via PUT request. Accepts flags for summary, body, priority, assignee, labels, components, parent, and custom fields with explicit confirmation before writing.
Core JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile), transitions/status changes (use jira-lifecycle), comments/attachments (use jira-collaborate), time tracking (use jira-time), bulk operations on 10+ issues (use jira-bulk), dependencies/blockers (use jira-relationships), branch names/PR descriptions (use jira-dev).
Creates new Jira issues using jirac CLI, extracting project key, issue type, summary, assignee, labels, priority, and custom fields from requests with interactive prompts.