ID 550537 - Backdrop nodes disconnect other nodes when added to a Nuke Studio export via Additional Nodes

 
Customer reported version:
Nuke 14.0v5
 
Customer reported platform:
macOS 13 Ventura
 
Steps to reproduce:
1) Launch Nuke Studio and Import some footage to the Timeline.
2) Right-click on the Clip and select Export...
3) With the Basic Nuke Shot export preset selected, click on Nuke Project File, and enable the Additional Nodes checkbox:

4) Click the Edit button, and then the Plus (+) button to add an Additional Node Setup.
5) Paste the following Backdrop node into the Script field. The z_order line is optional:

BackdropNode { inputs 0 name BackdropNode1 z_order 1}

6) After the Additional Nodes window looks like the following, click the OK button:

7) Click the Export button, open the resulting Nuke Project File, and observe the disconnect between the ModifyMetaData and AddTimeCode nodes:

 
Expected behavior:
Adding a Backdrop node as an Additional Node while Exporting from Nuke Studio should not change how other nodes in the Node Graph are connected.
 
Actual behavior:
If a Backdrop node is included in the Additional Nodes section of a Nuke Studio export, the resulting Node Graph will be disconnected, preventing renders from being successful. 
 
This can also lead to other Additional Nodes being positioned incorrectly, pictured below:

 
Workaround:
It's possible to place the Backdrop node and any other desired nodes inside a Group, which seems to prevent the disconnect from occurring:

Group {  name AdditionalNodes_Group  selected true }  BackdropNode {   inputs 0   name BackdropNode1   bdwidth 288   bdheight 276  }  Input {   inputs 0   name Input1  }  Grade {   name Grade1  }  Transform {   center {1024 778}   name Transform1  }  ColorCorrect {   name ColorCorrect1  }  Output {   name Output1  } end_group

 
Reproduced by Support in:
Nuke 14.0v5 - Windows 10, CentOS 7
Nuke 14.0v1 - Windows 10
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.0v1 - Windows 10, CentOS 7
 
Earliest version tested:
Nuke 10.0v1 - This issue appears to be in all tested versions of the product