OVERALL RATINGS
INSTALLS
2
SUPPORT
- Partner Supported
TRUST SIGNALS
- Requires
- JIRA
- Works with
- CONFLUENCE
Key highlights of the appFind and fix broken legacy URLs in Jira Cloud after migrating from Data Center or Server
Supporting media
Editions New
This app offers two different editions - Standard and Advanced. You can start a free trial of either edition, and change your edition anytime during or after the trial.
Standard
Onboard your team and scale fast
Includes:
URL Scanning
Fix URLs
URL Mappings
Scheduled Scans
Key Resolution
Advanced
Unlock the full range of app features
Everything from Standard, plus:
Full Governance Engine
Regex Search Mode
Remote Link → Native Conversion
CSV/JSON Export
Audit Log Export
More details
Legacy URL Scanner for Jira helps Jira administrators clean up broken URLs after migrating from Jira Data Center or Server to Jira Cloud. Key Features: - Scan entire projects or individual issues for legacy URLs - Search across descriptions, summaries, comments, and custom fields - Preview all found URLs before making changes - Fix URLs individually or in bulk with one click - Support for linked issues (direct and indirect) - Define multiple legacy host URLs to scan for Perfect for organizations that have recently migrated to Jira Cloud and need to update references to old Jira instances. The app runs entirely on Atlassian infrastructure - no data leaves your Jira instance.
Resources
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policySecurity program
This app is not part of the Marketplace Bug Bounty program.
Integration permissions
Legacy URL Scanner for Jira integrates with your Atlassian app
Version information
Version 13.8.0•for Jira Cloud
- Release date
- Mar 20th 2026
- Summary
- Minor version update
- Details
Release Notes — Rate Limit Compliance:
What changed:
- API calls now respect Atlassian's Retry-After header on rate limit (429) responses instead of using fixed delays
- Bulk operations (delete filters, attachments, versions) are now throttled in controlled batches to prevent rate limit triggers
- Scanner/board loading uses controlled concurrency instead of unbounded parallel requests
Why:
Atlassian enforced new points-based API rate limits on March 2, 2026. These changes ensure all apps stay within the burst limits and correctly back off when rate-limited.- Payment model
- Paid via Atlassian
- License type
- Commercial