api
Execute a raw Jira REST API call through the jirac CLI, including GET, POST, PUT, DELETE, and PATCH requests to any Jira REST…
@mulhamnaInstall SkillDevelopment
Skill
/move-issue
Move a Jira issue to another project using Jira's native move semantics with jirac (not clone+delete)
Claude Code
$ npx -y skills add mulhamna/jira-commands --skill move-issue --agent claude-code
Codex
$ npx skills add mulhamna/jira-commands --skill move-issue -a codex -y
Cursor
$ npx skills add mulhamna/jira-commands --skill move-issue -a cursor -y
Gemini CLI
$ npx skills add mulhamna/jira-commands --skill move-issue -a gemini-cli -y
GitHub Copilot
$ npx skills add mulhamna/jira-commands --skill move-issue -a github-copilot -y
OpenCode
$ npx skills add mulhamna/jira-commands --skill move-issue -a opencode -y
Windsurf
$ npx skills add mulhamna/jira-commands --skill move-issue -a windsurf -y
SKILL.md
move-issue.SKILL.mddescription: Move a Jira issue to another project using Jira's native move semantics with jirac (not clone+delete)
Move an issue across projects using `jirac`. This uses Jira's native move — the issue keeps its history, comments, attachments, and worklogs. This is different from `clone --move`, which creates a new key and deletes the original.
Steps: 1. Check that `jirac` is available by running `jirac --version`. If missing, tell the user to install it (`cargo install jira-commands`). 2. Extract from the user's request:
- source issue key
- target project key
- target issue type (optional — defaults to the current issue type name in the destination)
3. Confirm intent — moves can drop incompatible custom-field values and reassign workflow. 4. Run `jirac issue move <KEY> <PROJECT> [--issue-type <TYPE>]`. 5. Report the new key (Jira always re-keys on move) and link to view it with `jirac issue view <NEW_KEY>`.
Notes:
- Issue **key changes** (PROJ-123 → OTHER-45 or similar).
- Comments, attachments, worklogs, links, and history are **preserved**.
- If the target project does not have the same issue type, pass `--issue-type` with the closest equivalent (e.g. `Task`).
- Use `change-type` instead when staying inside the same project.
Examples:
- "move PROJ-123 to OTHER project" → `jirac issue move PROJ-123 OTHER`
- "move PROJ-50 to NEW project as a Task" → `jirac issue move PROJ-50 NEW --issue-type Task`
Read more
description: Move a Jira issue to another project using Jira's native move semantics with jirac (not clone+delete)
Move an issue across projects using `jirac`. This uses Jira's native move — the issue keeps its history, comments, attachments, and worklogs. This is different from `clone --move`, which creates a new key and deletes the original.
Steps: 1. Check that `jirac` is available by running `jirac --version`. If missing, tell the user to install it (`cargo install jira-commands`). 2. Extract from the user's request:
- source issue key
- target project key
- target issue type (optional — defaults to the current issue type name in the destination)
3. Confirm intent — moves can drop incompatible custom-field values and reassign workflow. 4. Run `jirac issue move <KEY> <PROJECT> [--issue-type <TYPE>]`. 5. Report the new key (Jira always re-keys on move) and link to view it with `jirac issue view <NEW_KEY>`.
Notes:
- Issue **key changes** (PROJ-123 → OTHER-45 or similar).
- Comments, attachments, worklogs, links, and history are **preserved**.
- If the target project does not have the same issue type, pass `--issue-type` with the closest equivalent (e.g. `Task`).
- Use `change-type` instead when staying inside the same project.
Examples:
- "move PROJ-123 to OTHER project" → `jirac issue move PROJ-123 OTHER`
- "move PROJ-50 to NEW project as a Task" → `jirac issue move PROJ-50 NEW --issue-type Task`
Ships withjira-commands
Jira on the command line. jirac is a Jira command-line client written in Rust. It ships as a single binary with no runtime dependencies and runs on macOS, Linux, and Windows.
5429 skills
Stars on GitHub
Momentum
- stars in total
- 54
Other skills on jira-commands.
@mulhamnaInstall Skillbatch
Run mixed Jira operations (create, update, transition, archive) from a single JSON manifest file using jirac batch
@mulhamnaInstall Skillbulk-comment
Add the same Markdown comment to multiple Jira issues with jirac, either by JQL query or explicit issue keys
@mulhamnaInstall Skillbulk-create
Create multiple Jira issues at once from a JSON manifest file using jirac bulk-create
@mulhamnaInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about move-issue.
- Which coding agents can use move-issue?
- move-issue installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.