Bulk Release Archiver for Jira helps Jira administrators and project administrators find stale releases and archive many of them safely without deleting release history.
Where to find it
Open a Jira project and go to:
Project settings → Apps → Bulk Release Archiver
What you can do
- Find old releases by age.
- Filter released or unreleased versions.
- View active or archived releases.
- Search by release name.
- Show overdue releases.
- Select releases across pages.
- Archive selected active releases in bulk.
- Restore selected archived releases.
- Review an explicit confirmation before any change.
- See progress and individual failures during a bulk operation.
Recommended cleanup workflow
- Open Bulk Release Archiver in Project settings.
- Start with Cleanup candidates.
- Review the filtered releases.
- Adjust the age cutoff if needed.
- Select the releases you intend to archive.
- Choose Archive selected.
- Read the confirmation, especially if any unreleased versions are included.
- Confirm the operation.
- Review the completion result and retry any isolated failures if necessary.
What "Cleanup candidates" means
By default, the app shows releases that are:
- released;
- not already archived;
- dated more than 12 months ago.
This is a review aid, not an automatic decision. The app never archives a release until an authorized user explicitly selects and confirms it.
Archive vs delete
Bulk Release Archiver does not delete releases.
Archiving keeps the release in Jira and allows it to be restored later. Atlassian states that archived releases are not intended to count toward the 15,000 releases-per-space limit, whose enforcement is rolling out progressively. See https://support.atlassian.com/jira-cloud-administration/docs/data-limits-and-guardrails/ for current platform guidance.
Restore an archived release
- Set Archive state to Archived.
- Select the release or releases.
- Choose Restore selected.
- Confirm.
Bulk-operation limit
A single archive or restore operation is limited to 1,000 releases. If a filtered set is larger, process it in more than one operation.
Permissions
The app uses Jira's existing authorization.
To archive or restore releases, the signed-in user needs the Jira permission required by the project-version update API, normally Administer Projects for that project or Jira administrator permission.
If Jira returns a permission error, the app will not bypass it.
Licensing
Bulk Release Archiver for Jira is a Paid via Atlassian Marketplace app.
A valid license is required to archive or restore releases. Read/filter/preview behavior may remain visible when the installation is not licensed.
Data and privacy
The app is designed without an external backend or customer-data database. See the app's Privacy Policy for details.
Troubleshooting
"Permission required"
Ask a Jira administrator to confirm that your account has the Administer Projects permission for the current project.
A release failed while others succeeded
Bulk operations isolate failures. Review the failed item and use Retry failed. A release may have changed, been removed, or become temporarily unavailable during the operation.
I cannot find a release
Check:
- release status filter;
- archive-state filter;
- age filter;
- overdue-only setting;
- name search.
Then use Cleanup candidates to reset the main filters.
I selected more than 1,000 releases
The app caps one write operation at 1,000 releases. Finish the first batch, refresh, then process the next set.
Support
Email: hello@renewalhub.co.za Website: https://renewalhub.co.za
When reporting a problem, include:
- Jira project key (if appropriate to share);
- what action you attempted;
- the visible error message;
- approximate time of the error;
- browser type.
Do not email passwords, API tokens, or confidential Jira issue content.