You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A validation error prevents saving User Roles where that User Role contains invalid permissions. Impacts a small set of User Roles that were not correctly migrated in 2019.1
What I expected to happen
The User Role should be able to be modified
Steps to reproduce
Find a User Role that that has space only permissions in the system set, or system only permissions on the space set.
Modify the name (or anything) and try to save
Screen capture
Log exerpt
There was a problem with your request.
The following are not valid Space permissions: SpaceEdit, SpaceView, SpaceDelete, SpaceCreate.
Affected versions
2019.1 to current, including LTS
Octopus Server:
Workarounds
Make use of a different / newly created user role that you can set up correctly, until this is patched.
Links
NA
The text was updated successfully, but these errors were encountered:
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.
lockbot
locked as resolved and limited conversation to collaborators
Oct 15, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bugThis issue represents a verified problem we are committed to solving
The bug
A validation error prevents saving User Roles where that User Role contains invalid permissions. Impacts a small set of User Roles that were not correctly migrated in 2019.1
What I expected to happen
The User Role should be able to be modified
Steps to reproduce
Screen capture
Log exerpt
Affected versions
2019.1 to current, including LTS
Octopus Server:
Workarounds
Make use of a different / newly created user role that you can set up correctly, until this is patched.
Links
The text was updated successfully, but these errors were encountered: