Blog ·
Archive Jira issues: one at a time, in bulk, and on a schedule
To archive Jira issues in Jira Cloud, open the work item, select More actions, choose Archive and confirm. The item leaves the space's boards, backlog and dashboards, becomes read-only, and waits under Archived work items until somebody restores it. Archiving is a feature of the Premium and Enterprise plans, and as of October 2026 Jira Cloud has no bulk archive button: archiving many items at once goes through an Automation rule or the REST API.
That covers the single item. The rest of this guide covers what archiving actually changes, how to restore, how to archive in bulk, which items are worth archiving at all, and how to turn the cleanup into a routine that comes back without anyone remembering it.
A note on words. Jira Cloud has been renaming things, and much of the interface now says spaces for projects and work items for issues. This article uses both.
What archiving a Jira issue does #
Atlassian's own documentation puts it in two sentences:
Archive a work item if you want to remove it from your space without deleting it. If you archive a work item, it will only appear in Archived work items and can no longer be edited.
In practice that means three things:
- It disappears from the everyday views. Boards, backlogs and dashboards stop showing it, so filters and reports stop counting it.
- It is frozen. Nobody can edit an archived item until it is restored.
- It is reversible. You can restore it later, and it comes back to the space, dashboards, backlog and boards with editing switched back on.
That last point is the whole reason to archive rather than delete. Deleting a work item is permanent. Archiving is a way of saying "not now, but keep the record," which is the right answer for most old work.
You'll need the relevant space permissions to archive and restore, so if the option is missing, check your role in that space before assuming the feature is absent.
Archive a single Jira issue #
The steps, as Atlassian documents them (as of October 2026):
- Open the work item, either in the side bar or full screen.
- Select More actions (the three dots).
- Select Archive and confirm.
You can't archive a subtask by itself. Archive its parent instead, and every subtask attached to that parent is archived with it.
Restore an archived item #
Restoring works from two places:
- From the list. Go to Archived work items, tick the checkbox beside the item and select Restore.
- From the item itself. Open it and select Restore from the banner, or More actions and then Restore.
To restore several at once, select multiple items on the Archived work items page, using the checkboxes, Ctrl or Command to pick individual items, or Shift for a run of adjacent ones, then select Restore.
A subtask follows its parent here too. To bring one back, open it from Archived work items and select Restore parent work item, which restores the parent and all of its subtasks together.
Note the asymmetry: restoring in bulk is built in, archiving in bulk is not.
Archive Jira issues in bulk #
Atlassian's knowledge base is direct about it, as of October 2026: you can archive individual work items natively, "but bulk archiving is not currently available in the UI." Its supported workaround is an Automation rule that finds the items with JQL and archives them through the REST API.
The shape of that rule:
- In Global automation, create a new rule.
- Pick a trigger. The knowledge base suggests Manual or Scheduled as the likely best choices.
- Add the Lookup work items action with a JQL query for the items to archive.
- Add a Send web request action: a
PUTtohttps://<your-site>.atlassian.net/rest/api/3/issue/archive, with a custom body listing the keys from the lookup, authorised with a user API token.
Two limits decide how far one run gets:
| Limit | Value (as of October 2026) | What it means |
|---|---|---|
| Archive API, per request | Up to 1,000 work items | One call can archive a large batch |
| Lookup work items action | Up to 100 work items | A rule built on lookup archives 100 per run |
| Automation executions, Premium | 1,000 per licensed user | Each run counts against the monthly allowance |
So a rule that uses Lookup work items archives at most 100 items each time it runs. For a backlog of several thousand, either run it repeatedly or page through the JQL results. Check your execution allowance before you schedule something that fires often; how Automation counts runs is covered in Jira Automation pricing, and the full set of service limits is in Jira Cloud automation limits.
The API token in that rule belongs to a person. If that person leaves and the token is revoked, the rule starts failing. Use a token you can account for, and look at the rule's audit log now and then.
Which Jira issues to archive #
Archiving is only useful if the query behind it is one you trust. Some JQL that picks out good candidates:
| What to archive | Example JQL |
|---|---|
| Done long ago | statusCategory = Done AND resolved <= -180d |
| Abandoned and untouched | statusCategory != Done AND updated <= -365d |
| Won't do, closed | resolution = "Won't Do" AND resolved <= -90d |
| A finished epic's leftovers | parent = ABC-123 AND statusCategory = Done |
Adjust the space and the windows to your team. Two cautions:
- Look before you archive. Run the JQL as a filter first and scan the list. An item that is still referenced from a live page, a linked incident or an audit trail may be better left where it is.
- "Abandoned" is a judgement, not a date. An open item nobody touched in a year might be dead, or might be the one thing waiting on a decision. Archiving it is reversible, which is why it beats deleting, but the person who owns that space should be the one to say yes.
That second caution is why a fully automatic archive rule on open work is risky. Archiving finished work on a timer is safe; archiving unfinished work on a timer quietly hides a decision. For the "is this still alive" pile, the better routine is a person reviewing the filter and archiving what they agree with. The wider set of checks that keep a space trustworthy is in Jira hygiene.
Make the archive cleanup a routine #
The pattern most teams settle into has two halves:
- The safe half runs itself. A scheduled Automation rule archives done-and-old items once a month, using the bulk approach above.
- The judgement half lands on someone's desk. Once a quarter, a person opens the "untouched for a year" filter, decides what stays, archives the rest, and closes the ticket.
The first half is an Automation rule. The second half needs a ticket that shows up on time, assigned to the right person, with the filter linked and the steps written down. That is a recurring work item, and the usual ways to make one are compared in Jira recurring tasks.
Recurring Work Items for Jira does that second half. A space admin writes the rule once: the work item type, summary, description with the filter link, assignee, due date, labels and an ordered list of subtasks such as "review the untouched filter", "check linked incidents", "archive the agreed items". The work item appears in that space on the schedule you set, quarterly in this case. It does not archive anything itself. It makes sure the review happens.
A few details that matter for this job:
- It runs on its own scheduler, so it consumes no Jira Automation quota. That leaves the allowance for the bulk archive rule.
- Dynamic titles. Titles and dates can carry tokens, so the ticket reads "Archive review, Q4 2026" instead of repeating last quarter's title.
- Working days and holidays. A rule can be set to skip weekends and holidays, so the review is not created on a day nobody is in.
- A history per rule. Every run, created, skipped or failed, is recorded with the reason, so you can tell whether the quarterly review was created.
- One space at a time. Rules belong to one space, so a team can run its own cleanup without touching anyone else's.
It is free for up to 10 users and listed on the Atlassian Marketplace.
When the manual way is enough #
You may not need any of this:
- A small space. If a quarter produces a few dozen finished items, archiving them by hand from the item view takes minutes.
- A Standard or Free plan. Work item archiving is a Premium and Enterprise feature. On other plans the honest options are a filter that excludes old work, or a resolution and a board filter that hides it.
- No one owns the cleanup. A schedule cannot create ownership. If nobody is going to review the list, start by deciding who that is.
Frequently asked questions #
Can I archive Jira issues on the Standard plan? As of October 2026, Atlassian lists work item archiving as available on Premium and Enterprise plans.
Does archiving delete the item? No. It removes the item from the space's views and makes it read-only. You can restore it from Archived work items.
Can I archive a subtask alone? No. Archive the parent, and its subtasks go with it. Restoring the parent brings them back.
Is there a bulk archive button? Not in the Jira Cloud UI as of October 2026. Bulk restore exists; bulk archive goes through an Automation rule calling the archive API, or a Marketplace app.
How many items can one rule archive? The archive API accepts up to 1,000 per request, but a rule that finds items with Lookup work items gets at most 100 per run.