Problem summary Within the Node Graph, it is possible to extract the nodes contained within a Group node, collapse it, and add them directly the Node Graph. This process can be achieved through using the 'Expand Group' (Cmd/Ctrl + Alt + G) option when the Group node is selected.
It has been discovered that if the Group node you are expanding contains disconnected nodes without an input, these nodes will be incorrectly connected to the Group's input node in the Node Graph.
Customer reported version nuke.11.3v6
Customer reported platform centos7
Steps to reproduce
1) Within a new Nuke session, create a NoOp node
2) Create a Group node, connecting this to the NoOp node
3) Enter the Group node (Cmd/Ctrl + G)
4) Within the Group node, create two NoOp nodes
5) Connect the first NoOp node to the Input
6) Create a Merge node, connecting the A stream to the second NoOp (ensuring it has no input) and the B stream to the first NoOp
7) Connect the Merge output to the Group's Output
8) Close the Group node's tab, and return to the Node Graph
9) With the Node Graph, select the Group node and expand using the 'Cmd/Ctrl + Alt + G' shortcut Result: Both NoOp nodes are connected to the source, even though only one has an Input source in the Group.
Expected behaviour Nodes expanded into the Node Graph from a Group node, should only connect if connected to an Input.
Actual behaviour Disconnected nodes from the Group node are connect to the Group nodes input within the Node Graph
Workaround Unknown.
Reproduced by support This bug has been reproduced in: Nuke 12.2v5 - Windows 10 - MacOS 10.15.6 - CentOS 7 Nuke 12.2v1 - Windows 10 Nuke 12.1v1 - Windows 10 Nuke 12.0v1 - Windows 10 Nuke 11.3v1 - Windows 10 Nuke 11.2v1 - Windows 10 Nuke 11.1v1 - Windows 10 Nuke 11.0v1 - Windows 10 Nuke 10.5v1 - Windows 10 Nuke 10.0v1 - Windows 10 Nuke 9.0v1 - Windows 10
Earliest version tested Nuke 9.0v1 - This issue appears to be in all versions of the product
