Bug 32286

Summary: Closing the module does always warn the user about unsaved changes
Product: UCS Reporter: Dirk Wiesenthal <wiesenthal>
Component: System setupAssignee: UCS maintainers <ucs-maintainers>
Status: RESOLVED WORKSFORME QA Contact:
Severity: minor    
Priority: P5 CC: best, gohmann, klaeser
Version: UCS 3.1   
Target Milestone: UCS 3.x   
Hardware: Other   
OS: Linux   
What kind of report is it?: --- What type of bug is this?: ---
Who will be affected by this bug?: --- How will those affected feel about the bug?: ---
User Pain: 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:

Description Dirk Wiesenthal univentionstaff 2013-08-21 14:17:06 CEST
When using the "close" button at the bottom of the module there is always the question whether one really wants to close the module, unsaved changes would be lost. But maybe no changes were made? This should be checked before bothering the user.
Comment 1 Florian Best univentionstaff 2014-11-24 12:36:01 CET
In UCS4.0 the code which asks for it is commented out. So it is never asked.
Comment 2 Alexander Kläser univentionstaff 2015-01-13 13:08:55 CET

*** This bug has been marked as a duplicate of bug 36700 ***
Comment 3 Alexander Kläser univentionstaff 2015-01-13 13:09:26 CET
(In reply to Alexander Kläser from comment #2)
> 
> *** This bug has been marked as a duplicate of bug 36700 ***

Wrong bug.
Comment 4 Florian Best univentionstaff 2017-02-09 17:16:23 CET
Doesn't happen in UCS 4.2