ID 364998 - Transform concatenation behaves differently than it used to in Nuke 11.0 and earlier

Problem summary
Transform concatenation behaves differently than it used to in Nuke 11.0 and earlier.

The bounding box and filter behave much more erratically in Nuke 11.2 when concatinating the transformations of 2 or more Transform nodes.

Customer reported version
nuke.11.2v3

Customer reported platform
windows7

Steps to reproduce

1) Open the attached script and view it from the Transform_MatchMove node.

2) Notice the erratic behaviour of the bounding box and the filter.

3) If you open the same script in Nuke 11.0v4, you will notice that this erratic behaviour does not occur.

Reproduced by support

This bug has been reproduced in:
Nuke 11.2v3 - Windows 10 - Linux CentOS 7 -macOS 10.13 (High Sierra)

Nuke 11.2v2 - Windows 10

Nuke 11.1v6 - Windows 10 - Linux CentOS 7 -macOS 10.13 (High Sierra)

Nuke 11.1v3 -macOS 10.13 (High Sierra) - Regression

Nuke 11.1v2 - Linux CentOS 7 - Regression

Nuke 11.1v1 - Windows 10 - Regression

Unable to reproduce bug in:

Nuke 11.1v2 -macOS 10.13 (High Sierra)

Nuke 11.1v1 - Linux CentOS 7

Nuke 11.0v4 - Windows 10

Earliest version tested
Nuke 11.0v4
- This issue no longer appears in this version and has regressed

Expected behaviour
The Transform nodes should concatenate and, in this case, show a small amount of jitter.

Actual behaviour
Both the bounding box and filter behave erratically in Nuke 11.1 and Nuke 11.2.