Jira issues when converted from legacy editor show as 'Data Card - Link' in the new editor, this affects Page Properties Report macro

Issue Summary

Jira issues when converted from legacy editor show as 'Data Card - Link' in the new editor
The Jira issues are rendered properly in the new editor after conversion. However, this is causing issues with the 'Page Properties report' macro, where this Jira shows a normal link instead of a card.
However, if we replace this 'data link' (Jira issue converted from Legacy editor) as a Jira issue on the 'Page Property' macro. We are able to see the Jira issue as expected in Page Properties Report macro.

Steps to Reproduce

1. Create a page in legacy editor
2. Add Page Property macro and add the Jira issue inside the table - (Page 1)
3. Create another page with Page Property Report macro - (Page 2)
4. The Jira issue on Page 2 looks as expected at the moment.
5. Convert Page 1 to the new editor.
6. Check Page 2 and now we'll see the Jira issue displayed as a normal URL, not a card.

Expected Results

The 'Jira issue' in the legacy editor should get converted as a 'Jira issue' on the new editor.

Actual Results

The 'Jira issue' in the legacy editor is getting converted to a 'Data card link' in the New editor.

Workaround

Manually replace 'Data Card link' with a 'Jira issue' after converting Page 1 (Page containing Page Property macro). Now it shows as expected on Page 2 (Page containing Page Property Report macro).

Replacing multiple issues in multiple pages is not a viable solution and hence this issue needs to be addressed.