Cannot edit variables after upgrade from 2018.2.8 to 2018.3.1

[Leslie]

The way we have security setup the developers can only edit variables in some environments. They were assigned to a team that had a user role with the permission VariableEdit. That team was then assigned to the project and the environments in that project in which the dev team was allowed to edit the variables. With the upgrade to 2018.3.1 the developers can no longer edit variables. Instead of a save button, then now see a gray box that says “VARIABLEEDIT PERMISSION REQUIRED” 2018.3.2 did not fix this

[Kenneth_Bates]

Hi Leslie,

Thanks for getting in touch! I’m very sorry you’re hitting this unintended and annoying bug! It’s currently a known bug we’ve recently introduced where users with the VariableEdit permission scoped to individual projects aren’t allowing these users to edit these variables. We have a fix going through and it should be shipped very soon. You can track this issue here.

Issue: Scoping VariableEdit permission to project removes the permission to edit variables in the project

Please don’t hesitate to reach out if you have any further questions going forward.

Kind regards,

Kenny

[Kenneth_Bates]

Hi Leslie,

I just wanted to quickly let you know that the fix to this issue has been shipped and available in 2018.3.3 which you can download here.

Let me know how you go and if you have any further questions!

Kind regards,

Kenny