Issue Summary

When importing data using Jira Cloud Backup & Restore / Site Import with the option to replace the source site URL with the destination site URL, the replacement logic strips the https:// protocol prefix. As a result, destination URLs in comments and text fields become incomplete (e.g., destination-site.atlassian.net/browse/... instead of https://destination-site.atlassian.net/browse/...), preventing them from rendering as clickable smartlinks or markdown links.

Steps to Reproduce

1. Take a site backup containing Jira work items with comments or custom text fields linking to the source site (e.g., https://source-site.atlassian.net/browse/ABC-123).
2. Perform a Cloud Site Import / Backup & Restore into a destination Jira Cloud instance.
3. Configure the URL replacement to map the source site URL to the destination site URL.
4. Inspect imported work items, comments, and text fields where the source site URLs were replaced.

Expected Results

Source site URLs are replaced with the full destination URL including the https:// protocol (e.g., https://destination-site.atlassian.net/browse/ABC-123), and links render as clickable hyperlinks/smartlinks.

Actual Results

The https:// prefix is removed during replacement, leaving bare URLs (e.g., destination-site.atlassian.net/browse/ABC-123). These are not parsed as valid links and remain plain, unclickable text.

Workaround

Currently, there is no native workaround post-import other than manually editing or using API scripts to update comments and text fields to prepend https://.