Steps to reproduce:
- Create gameobject. Let its name be "Parent". Apply any non-uniform scale and rotation transformations.
- Create another gameobject. Set it to be a child of "Parent" gameobject. This gameobject will become incorrectly transformed.

Why is this by design?
A transform defined by position, rotation and x/y/z scale cannot represent the local transform needed to define the child transform relative to the rotated and non-uniformly transformed parent (as that would be a shear transform). To overcome this, we would have to represent transforms as fully customizable 4x4 matrices (which is generally considered inconvenient).