ID 599224 - Comp container's timecode changes when the Nuke script is saved on different frames

Problem summary
Comp container's timecode changes when the Nuke script is saved on different frames

Customer reported version
nuke.14.1v6

Customer reported platform

Linux

Steps to reproduce

1) Launch Nuke Studio

2) Import any footage and add it to a sequence

3) Right click the track item>Create Comp, and select a directory to create the comp in

4) Select the comp container on the timeline and press Alt+D to open it's metadata panel. Check the timecode, it should be the same as the clip's  timecode.

5) Double click the comp container to open the Nuke script

6) Change the playhead to any other frame, and save the Nuke script, the timecode in the metadata panel will change:

Expected behaviour
For the timecode on the comp container to be consistent, no matter which frame the playhead is on the Nuke script.

Actual behaviour
The timecode changes based on where the playhead is in the Nuke script

Workaround
Unknown.

Reproduced by support
This bug has been reproduced in:
Nuke Studio 16.0v2 - Windows 10

Nuke Studio 13.0v1 - Windows 10

*Also reproduced by the developers

Earliest version tested
Nuke Studio 13.0v1- This issue appears to be in all tested versions of the product