Label Cleanup for Jira
Try or install on the Atlassian Marketplace.
Rename, merge and delete Jira labels across all your issues. Every change starts with a dry run, only the exact spelling you choose is changed, notifications are off by default, and any change can be undone for 30 days. Jira Cloud has no built-in way to edit labels (JRACLOUD-33672).
Getting started
- Install the app from the Atlassian Marketplace.
- Open Jira Settings → Apps → Label Cleanup (Jira admins), or Apps → Label Cleanup (people an admin has allowed).
- On the Labels tab, find the label and click Clean up.
- Choose Rename, Merge into another label or Delete, optionally pick one project, and click Dry run.
- Check the numbers, then click Change.
Labels tab
- Counts are for the exact spelling. A badge shows other spellings that differ only by upper or lower case, for example "Also as Bug (6), BUG (3)".
- Very large labels show a combined count marked "all spellings"; the dry run always gives the exact number.
- Click a label to open it in Jira search.
Dry run
The dry run shows the number of issues with exactly that spelling, how many already have the new label, the projects touched, example issue keys, and issues you can't edit (they are skipped). Nothing changes until you click Change. Delete asks you to type the label name. A dry run can be used for 24 hours.
Running a change
- Changes run in the background with a progress bar and an estimated time. You can leave the page.
- Jira processes about 3 issues per second, so 1,000 issues take about 5 minutes per step. A rename or merge is two steps (add the new label, then remove the old one).
- Changes use your own Jira permissions, so issue history shows your name.
- If a change is interrupted, it resumes automatically within a few minutes.
Undo
Click Undo on a finished change within 30 days. The old label goes back on every issue that lost it, and the new label is removed only where the change added it.
Settings (Jira admins)
- Who can use Label Cleanup: Jira admins always. Add allowed groups, or project roles (people with an allowed role can change labels only in that project).
- Notifications: off by default, so watchers get no emails. Turn on to send Jira's usual notifications.
- Speed limit: Jira requests per hour for your site (default 10,000). Big changes pause and continue automatically when the limit is reached.
People also need Jira's Make bulk changes global permission, and Browse and Edit issues in each project.
Limits
- Up to 200,000 issues per change; run it again for the rest.
- Issues in archived projects or in statuses that block editing are skipped.
- A deleted label can keep showing in Jira's suggestions for a while.
- Automation rules that react to label changes may run for each changed issue.
Data
Label Cleanup stores its settings and, for 30 days, the issue ids each change touched (for undo) in Atlassian Forge storage. It makes no calls outside Atlassian. Uninstalling removes the stored data; labels on issues stay as they are.
Support
Email support@funaticilluminations.com with your Jira site URL and what you tried.