Univention Bugzilla – Bug 32430
Remove "OU-" prefixes in UMC wizards
Last modified: 2019-02-05 21:26:41 CET
For simplicity/usability the OU prefixes in the UMC wizard should be removed. In single school environments this is unneccessary since in most cases there will be no naming conflict for groups etc. In multi-ou environments the users may be confused because the windows file permission dialogs, the UDM or the local filesystem (UCS/UCC) will show other group names than the UCS@school wizards. +++ This bug was initially created as a clone of Bug #32337 +++ I have seen this in two customer environments: - classes/groups exist without OU-prefix (e.g. klasse10a) - add a new user with the wizard, assign this user to the said class (klasse10a) - instead of adding the user to the existing class, a new class is created WITH the OU-prefix (e.g. GYM123-klasse10a) and its only member is the newly created user This might be related to Bug 31663
Suggestion: All UMC modules directly show the real group names. The users will get confronted with them at least in windows share dialogs. Why not showing them in all dialogs. The wizard for creating a class (group) prefills the OU prefix into the group name field. The user may change/remove the prefix or use it as suggested by the wizard. Ideally the wizard warns the user if he removes the prefix but does not prevent the user from doing so. This would make it hopefully transparent to the user.
Ticket: 2015011521000091 Customer requested a uniform representation of the group names (always with prefix) to not confuse users/teachers with different names in different places (like in windows security dialog and share names).
There is a Customer ID set so I set the flag "School Customer affected".
This issue has been filled against UCS@school 3.2. The maintenance with bug and security fixes for UCS@school 3.2 has ended on Dec 31, 2016. Customers still on UCS 3.x are encouraged to update to UCS 4.3 (or later). Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.