Hello @r0den ,
Thank you for sharing the report.
This is a known issue for which a fix was released mid-February. Since the linked PUR had been submitted before that release, the fix was not applied to it, but the team is working on the solution to resolve the problem for such PURs too.
As there is an ongoing discussion in another report, I’m going to mark this case as a duplicate. However if you come across any PURs that were submitted after mid-February but do not appear in the Issue Tracker, please leave examples in this thread.
Please let me know if you have any questions.
Kind regards,
Kasia