Issue Summary

Custom URL fields containing "notes://" protocols appear empty in the Issue View.

We have verified in the DB, the values are present correctly. However, the respective field values are not showing after upgrade. Also, if they try to add the field manually into an issue, it fails with "Not a valid URL" error.

Steps to Reproduce

• Upgrade to 10.3.24 or Install Jira 10.3.24. Behaviour is same in both scenarios.

• In case of upgrade custom URL field should be carried over. However, on a fresh installation, create a Custom Field of type URL Field.

• In case of upgrade, the issue in which the field was associated - the field does not shows up when viewing issue after upgrade.

• Observe that the field is hidden/empty in the Issue View. (in case of upgrade scenario where the field was there in previous version).

• Try to add the field to an issue screen and enter a value using the protocol: notes://SERVER/DATABASE/VIEW/DOCUMENT.

• Adding this field newly into an issue also throws an error Not a valid URL.

• Check atlassian-jira.log to see the WARN message: Not a valid URL.

Expected Results

The field should be carried over and allow notes://

Actual Results

The field is hidden/empty and cannot be added to issue screen.

The below exception is thrown in the atlassian-jira.log file:

2026-08-13 07:51:04,552+0200 http-nio-8080-exec-2 WARN fkrause 471x1630570x1 1ujhs9l 172.16.223.128,192.168.150.201 /rest/api/latest/issue/IAP-3087 [c.a.j.i.customfields.impl.AbstractSingleFieldType] Issue IAP-3087 has an invalid value 'notes://svdominonb.nb.deg.local/412565DA0054053B/A39D98CF5938EEA08525668D004CA96F/C72D5BC9B36B0514C1257CC30046C6EF' stored in the field 'Detailkonzept'. Not a valid URL2026-08-13 07:51:23,568+0200 http-nio-8080-exec-8 WARN fliebscher 471x1632440x6 1q2sng3 192.168.31.86,192.168.150.201 /rest/api/latest/issue/IAP-3087 [c.a.j.i.customfields.impl.AbstractSingleFieldType] Issue IAP-3087 has an invalid value 'notes://svdominonb.nb.deg.local/412565DA0054053B/A39D98CF5938EEA08525668D004CA96F/C72D5BC9B36B0514C1257CC30046C6EF' stored in the field 'Detailkonzept'. Not a valid URL 

Workaround

Converting the field type to "textfield" via SQL resolves the issue.