archive

Name: archive
Availability: InStock
Author: mulham

Archive Jira issues matching a user-specified JQL after a dry-run.

46|12|Updated Apr 15, 2026

Search Tags:#permissions #issue management #archiving #jira #jql #bulk operations

Ready to run

npx skills add https://github.com/mulhamna/jira-commands --skill archive-mulhamna

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: archive
Source: https://github.com/mulhamna/jira-commands/tree/main/plugin/skills/archive
Command: npx skills add https://github.com/mulhamna/jira-commands --skill archive-mulhamna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of safely finding and archiving the exact set of Jira issues matching a JQL query without accidentally affecting unrelated work.

Core Features & Use Cases

JQL-Driven Archiving: Archives issues by applying a user-provided JQL that can be precisely scoped by project, status, age, and resolution.
Safety via Dry-Run and Confirmation: Encourages verification of the matched issue set through a dry-run list before the destructive archive action.
Operational Reporting: Reports the number of issues archived and reminds users about permission requirements and query scoping best practices.

Quick Start

Ask to archive a scoped set of issues by providing the JQL, after reviewing the dry-run results, for example: "archive done issues older than 6 months in PROJ".

Frequently Asked Questions about archive

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

FAQPage Schema

How do I bulk archive Jira issues using JQL?▼

You can bulk archive Jira issues using JQL to precisely scope the target items by project, status, age, or resolution. The Skill performs a dry-run list for verification, validates explicit intent, and then executes the archive action to hide them from normal search.

What happens to Jira issues after they are archived?▼

When Jira issues are archived, they become hidden from standard JQL queries and normal search results, and they are set to read-only. This removes resolved work or large backlog items from active boards while preserving the historical data safely.

Can I preview which Jira issues will be archived before making changes?▼

Yes, the Skill runs a dry-run that generates a list of Jira issues matching your provided JQL before executing the destructive action. This allows you to verify the exact issue set and scope to prevent accidentally archiving unrelated work.

Do I need specific Jira permissions to archive issues in bulk?▼

Yes, executing bulk archive operations with JQL requires the appropriate Jira permissions for the targeted projects. The Skill respects Jira permissions and reports the total archived count while reminding you of query scoping best practices.

What is the best way to clean up resolved Jira issues older than 6 months?▼

The best way to clean up resolved Jira issues is to use JQL to scope the exact set, such as done issues older than 6 months in a project. After a dry-run verification, the Skill archives them to declutter boards and standard queries.