Bug 27251 - Return ohne Wirkung
Return ohne Wirkung
Status: CLOSED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: UMC
UCS@school 3.0
Other Linux
: P5 minor (vote)
: ---
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-23 12:36 CEST by Stefan Gohmann
Modified: 2023-06-12 15:39 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
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.103
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2012-05-23 12:36:45 CEST
Beim Bearbeiten von Räumen oder Gruppen in UCS@school übernimmt Return nicht die Änderung. Es muss immer auf Speichern geklickt werden.
Comment 1 Alexander Kläser univentionstaff 2012-06-01 15:12:03 CEST
Im JavaScript-Code muss dazu ein zusätzlicher Handler registriert werden.
Comment 2 Florian Best univentionstaff 2014-02-07 21:01:46 CET

*** This bug has been marked as a duplicate of bug 29756 ***
Comment 3 Florian Best univentionstaff 2014-02-07 21:02:25 CET
Ups, product was UCS@School
Comment 4 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:49:33 CET
This issue has been filled against UCS@school 3. The maintenance with
bug and security fixes for the last UCS@school version for UCS 3.x 
(→ 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.