Adding new variable to project with limited permissions to scopes deletes variables not in scope

[hnrkndrssn]

Repro:

• Create a new project
• Add two variables, VarDev & VarProd, scoped to dev and prod environments respectively
• As a DEV user, view the variables-- as expected we only see the VarDev variable
• As a DEV user, try to add VarNew variable-- as expected we get permission denied
• As an ADMIN user, grant the DEV user permissions to edit variables
• As a DEV user, try to save new variables again-- as expected we are now allowed.

Expected result: VarDev, VarProd, and VarNew variables should be present.

Actual result: VarDev and VarNew are present, while VarProd has been "deleted"

Source: http://help.octopusdeploy.com/discussions/problems/42649

[robpearson]

Failed to reproduce but customer has provided more detail including:

• additional steps/detail to reproduce
• audit log screenshot

Needs further investigation.

[zentron]

https://github.com/OctopusDeploy/OctopusDeploy/commit/1d3ebafbae2be2dcf3f3fd2ad482cec342464963
If the user's available environments changes while they are editing the variable set they will be prompted to reload the page. This is the same existing mechanism that is used currently if someone else has changed the variable set while the user makes changes.

[zentron]

Release Note: Updating project variables while the user's environment permissions have changed forces user to reload. This blocks a bug causing variables to be removed.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.