Bug 44633 - Creating a workgroup and adding users in one step, the users do not get a link to their shares in the logonscript
Creating a workgroup and adding users in one step, the users do not get a lin...
Status: CLOSED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: UMC - Classes / Teachers / Workgroup assignment
UCS@school 4.1 R2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-05-18 13:07 CEST by Christina Scheinig
Modified: 2023-06-12 15:39 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.171
Enterprise Customer affected?: Yes
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017051821000315
Bug group (optional): External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christina Scheinig univentionstaff 2017-05-18 13:07:34 CEST
A customer reported that creating a workgroup and adding users in one step, the listener module "ucs-school-user-logonscripts" is not triggered.
This causes the users not to get a link to their "Eigene Shares" in the logonscript.

Creating an empty workgroup and adding the users afterwards works fine.
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:43:24 CET
This issue has been filled against UCS@school 4.1 (R2). The maintenance with
bug and security fixes for UCS@school 4.1 (R2) has ended on 5th of April 2018.

Customers still on UCS 4.1 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.