2023.1.10 seems breaking "Move to Vault" for sessions with sub-connections
We use RDM with MSSQL DB and just updated from 2022.3.29.0 to 2023.1.10. While moving entries with sub-connections between vaults, only the base connection get's transferred. Sub-connections remain in the source vault. This definitely wasn't the case with the old version.
Can you reproduce this behavior?
Best regards
Hello,
Thank you for reporting this issue.
I have been able to reproduce the issue.
A ticket has been sent to the engineering department. Once a fix will be available, we will update this thread.
Thank you for your patience.
Best regards,
Érica Poirier
Thanks for the fast response and testing! So we will avoid moving stuff between vaults until a fix is available...
Best regards
Hi, any idea when a fix will be available?
Thank you and best regards
Hello,
Thank you for your feedback.
The ticket is still in the backlog. I will ask the engineering team if they can increase the priority on this ticket.
Thank you for your patience.
Best regards,
Érica Poirier
Hi Devolutions Team
I just wanted to confirm that the bug is finally fixed with 2023.2.22.0. I was a bit surprised that this bugfix was noted as a new feature, as we clearly use this function since many years.
I hope the time that it took to fix this function isn't the new normal. I reported quite some bugs in the past and got always good response times and timely fixes. I was a bit suprised that it took so long this time...
Thanks and best regards
Hello,
Thank you for your feedback and glad the fix is working on your end.
In fact the fix as been identified as an improvement because the new method RDM handles the sub entries are completely different than the legacy sub connections.
As for the time it took to fix the issue, it will depend on multiple factors and sometime some fixes take much more time to resolve than others.
But anyway, thank you very much for your patience on this case.
Best regards,
Érica Poirier