PackageLink AutoUpdate prevents proper rollback to earlier version of the place

Reproduction Steps

1. Create a place
2. Create a script file
3. Setup a package link on the script with autoupdate = true
4. Change some code in the script
5. Publish the new package version
6. Open a earlier version of the place from “Version History”

This becomes a big problem in multi-place projects with a lot of packages.

Expected Behavior

The code to be as it was in the earlier version of the place by auto-update being disabled on the packages to have a functional “Version History”

Actual Behavior

The code automatically updates to the latest version when you open the earlier version breaking the “Version History” feature.

Workaround

Don’t use AutoUpdate on packages, but if there are packages that has used AutoUpdate there is no way of going back to fix it.

Issue Area: Studio
Issue Type: Other
Impact: High
Frequency: Constantly
Date First Experienced: 2022-11-01 00:11:00 (+01:00)
Date Last Experienced: 2022-11-02 00:11:00 (+01:00)

3 Likes

Thank you for reporting the issue. We filed a ticket to our internal database.

2 Likes

Closing this bug as the behavior is expected. But, we have filed an internal feature ticket for providing the desired behavior for version history.