Issue Summary

Following the upgrade to Jira 11.3.10, URL custom fields that previously contained file:// links no longer display those values in the Jira UI (. While the data remains intact in the customfieldvalue database table, the new URL validation layer  treats these existing values as invalid and returns null to the display layer. This results in a perceived data loss for customers who rely on these fields to reference local or network resources.

Steps to Reproduce

• On a Jira version prior to 11.3.10 (e.g., 11.3.8), create a URL Custom Field.

• Create an issue and populate the field with a file:// link (e.g., file:https://server/path/document.pdf).

• Upgrade the Jira instance to version 11.3.10.

• View the issue created in Step 2.

Expected Results

The existing file:// value should be displayed in the UI, even if the scheme is now restricted for new inputs.

Actual Results

• The URL field appears completely blank in the Issue View.

• The REST API returns a null value for the field.

• CSV and XML exports omit the value.

• Note: A direct database query confirms the data still exists in the customfieldvalue table.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available