Bug: SureBackup "Start to..." doesn't work as expected

[Moebius]

Case # 00651060

Trying to solve a different issue with the Tech Support, I needed to run a point-in-time SureBackup job ("Start to..." and choosing date and time of (or just after) a past backup). It appeared that SureBackup does not behave as expected in this case.
The VMs of the application group start correctly from the restore point of the date and time chosen, but all the VMs of the linked job start from the most recent restore point instead. The "Start to..." command is ignored by the VMs of the linked job.

Am I missing something or this is a bug? The only way to test a backup other than the most recent is to instant-recover the VMs manually into an existing virtual lab and run the tests and scripts manually.

[foggy]

Lucio, this is a known v7 issue that is already addressed in the upcoming v8: currently linked jobs ignore the "Start to" setting and start from the most recent restore point. Sorry for inconvenience.

[Moebius]

Alexander, thank you. I did a search on this but didn't find anything. Good to know it is being addressed.