ID 479281 - Hiero/Nuke Studio always import the latest clip version when building track, even if the version number is defined in the preset/structure

Problem summary
Hiero/Nuke Studio always import the latest clip version when building track, even if the version number is defined in the preset/structure

Customer reported version
hiero.12.0v2

Customer reported platform
windows10

Steps to reproduce
1) Download the attached versioning_v###_####.exrs files and save them to the same folder
2) Open Hiero/Nuke Studio
3) Import the versioning_v001_####.exr and add it to the timeline
4) Right click the clip>Export...
5) Drag and drop the attached TESTPRESET.xml into the Local Export Preset bin, and close the Export dialog, making sure to save changes to export templates
6) Right click the clip>Build Track>From Export Structure
7) Select the TESTPRESET Export preset, notice the path points to versioning_v001_####.exr

​

8) Press Build, the VFX Track uses version v002, not v001 as specified in the preset

Expected behaviour
For Build track to use the preset from the Build track export dialog

Actual behaviour
The newest version of the clip is used, not the one defined in the preset

​

Workaround
Unknown.

Reproduced by support
This bug has been reproduced in:
Nuke Studio 13.0v2 - Windows 10, CentOS 7.5, macOS 11.3.1
Nuke Studio 12.0v1 - Windows 10
Nuke Studio 11.0v1 - Windows 10
Nuke Studio 10.0v1 - Windows 10, CentOS 7.5 * {filepath} token doesn't exist in this version, so you need to change the preset to point to where the file is located
Nuke Studio 9.0v1 - Windows 10, macOS 11.3.1

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