Bug Remove lock not working for administrators

Hello, I am trying to manually remove locks in order to get around this issue:

https://forum.unity.com/threads/ser...ned-lock-that-should-no-longer-exist.1478346/

But upon attempting to remove the lock it says "only the server administrator can remove locks".
The thing is, my account has administrator status with all permissions enabled and yet I'm still getting this error.

At this point, there seems to be no way around the issue and it is blocking work.
Any help would be appreciated, thanks.

 

@nhpatt
I just tried it in the Unity dashboard and it works, thank you! I was only trying it in the client when I was getting this message. This is very helpful.

@carlosalba1985
Thanks. So in this case, the message actually means "owner" then and not the "administrator" group which is a little misleading.

Would it be possible to have a permission for this that we can add to groups (e.g. admin) rather than only a specific account? With the frequency of locking issues we are finding, having only one account with this permission is not enough for us.
I'm happy that we can do this in the dashboard, but it would be great to be able to do it in the client as well.

To be more clear on this, I need to unlock things, but it would not be good to remove unlock permission from the existing server owner.

 

Thanks! I didn't realise the owner could be set to a group since it was a specific user by default!

The reason we have to unlock frequently because with the new smart locks we quite often run into issues (maybe bugs?) that prevent us checking out or merging files. Sometimes for example it seems to think the latest version of a file is on a different branch, even though the branch was already merged to main. The lock is still retained even though the changes were merged, and there are some other little discrepancies like this seem to pop up randomly.

There is also the issue where a user makes a change on a branch, and the branch cannot be merged yet but it is blocking another user from making another change to the same file. In this case the team wants to discard the change in the first branch so that the second user can make the change. This requires manual unlocking.

Thanks again for the tip about setting a group as the owner, that's very helpful.