Comment #2 says this issue was verified on a 1.21 environment so on that basis 1.21 will need to be fixed.
Comment #2 says this issue was verified on a 1.21 environment so on that basis 1.21 will need to be fixed.