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
/archive
Archive Jira issues matching a JQL query with jirac
Claude Code
$ npx -y skills add mulhamna/jira-commands --skill archive --agent claude-code
Codex
$ npx skills add mulhamna/jira-commands --skill archive -a codex -y
Cursor
$ npx skills add mulhamna/jira-commands --skill archive -a cursor -y
Gemini CLI
$ npx skills add mulhamna/jira-commands --skill archive -a gemini-cli -y
GitHub Copilot
$ npx skills add mulhamna/jira-commands --skill archive -a github-copilot -y
OpenCode
$ npx skills add mulhamna/jira-commands --skill archive -a opencode -y
Windsurf
$ npx skills add mulhamna/jira-commands --skill archive -a windsurf -y
SKILL.md
archive.SKILL.mddescription: Archive Jira issues matching a JQL query with jirac
Archive all issues matching a JQL query using `jirac`. Archive is destructive — issues are hidden from regular search and become read-only.
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 or build a JQL query from the user's request that scopes the archive cleanly (project, status, age, resolution). 3. Dry-run the JQL via `jirac issue list --jql '<JQL>'` so the user can see the affected set before archiving. 4. Confirm intent explicitly — archive is irreversible without admin assistance. 5. Run `jirac issue archive --jql '<JQL>'` (omit `--force` to keep the confirmation prompt; add `--force` only after explicit confirmation in agent flows). 6. Report how many issues were archived.
Notes:
- Archive requires sufficient Jira permissions (typically Project Administrator).
- Archived issues remain in the database but are hidden from boards, dashboards, and standard JQL searches by default.
- Prefer scoping by `project`, `resolution`, `updated`, and `status` — broad queries can archive far more than expected.
- For non-destructive cleanup, consider `bulk-transition` to a "Won't Do" or "Closed" status first.
Examples:
- "archive done issues older than 6 months in PROJ" → `jirac issue archive --jql 'project = PROJ AND resolution = Done AND updated < -180d'`
- "archive all 'Won't Do' items in PROJ older than 90 days" → `jirac issue archive --jql 'project = PROJ AND status = "Won''t Do" AND updated < -90d'`
- "archive released old work" → `jirac issue archive --jql 'project = PROJ AND fixVersion in releasedVersions() AND updated < -365d'`
Read more
description: Archive Jira issues matching a JQL query with jirac
Archive all issues matching a JQL query using `jirac`. Archive is destructive — issues are hidden from regular search and become read-only.
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 or build a JQL query from the user's request that scopes the archive cleanly (project, status, age, resolution). 3. Dry-run the JQL via `jirac issue list --jql '<JQL>'` so the user can see the affected set before archiving. 4. Confirm intent explicitly — archive is irreversible without admin assistance. 5. Run `jirac issue archive --jql '<JQL>'` (omit `--force` to keep the confirmation prompt; add `--force` only after explicit confirmation in agent flows). 6. Report how many issues were archived.
Notes:
- Archive requires sufficient Jira permissions (typically Project Administrator).
- Archived issues remain in the database but are hidden from boards, dashboards, and standard JQL searches by default.
- Prefer scoping by `project`, `resolution`, `updated`, and `status` — broad queries can archive far more than expected.
- For non-destructive cleanup, consider `bulk-transition` to a "Won't Do" or "Closed" status first.
Examples:
- "archive done issues older than 6 months in PROJ" → `jirac issue archive --jql 'project = PROJ AND resolution = Done AND updated < -180d'`
- "archive all 'Won't Do' items in PROJ older than 90 days" → `jirac issue archive --jql 'project = PROJ AND status = "Won''t Do" AND updated < -90d'`
- "archive released old work" → `jirac issue archive --jql 'project = PROJ AND fixVersion in releasedVersions() AND updated < -365d'`
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 Skillbulk-transition
Bulk transition multiple Jira issues with a JQL filter through the jirac CLI
@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 archive.
- Which coding agents can use archive?
- archive 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.