The bug was closed last week and the fix will be available in yast2-users 3.1.53 (https://github.com/yast/yast-users/pull/104). Thanks for reporting.