You can just attach the project in your response. I am downloading the original test project to verify that as well. I did verify this in a development stream and not the official 4.14.2 hotfix.
I can confirm it occurs in the test project I provided in the original report. I think what happened is that the issue was also being reported on another internal project and the fix went in for that issue, and just never made it over to the 4.14.2 hotfix.
I have re-opened the report so our engineers can get it resolved.
Cheers,
H