ID 594164 - Setting nuke.untitled no longer has any effect

Problem summary:
Setting nuke.untitled no longer has any effect
 
Customer reported version:
Nuke 14.1v6
 
Customer reported platform:
CentOS 7
 
Steps to reproduce:
1) Launch Nuke and open the Script Editor window
2) Execute the following two lines of code:

nuke.untitled = "some_test_name" nuke.scriptClear()

3) Observe how the unsaved Nuke script is still named "Untitled":

 
Expected behavior:
Setting nuke.untitled to a custom string should change the default name of new unsaved Nuke Scripts.
 
Actual behavior:
Unsaved Nuke scripts cannot have their name changed by setting nuke.untitled, as was possible in previous versions of Nuke:

 
Workaround:
No known workaround at this time.
 
Reproduced by Support in:
Nuke 15.1v5 - Windows 10, macOS 14 Sonoma
Nuke 14.0v1 - Windows 10
Nuke 13.0v1 - Windows 10, macOS 14 Sonoma -- Regression
 
Unable to reproduce bug in:
Nuke 12.2v11 - Windows 10, macOS 14 Sonoma
 
Earliest version tested:
Nuke 12.2v11 - This issue doesn't appear in this version and has regressed