Bug 32286 – Closing the module does always warn the user about unsaved changes

Bug 32286 - Closing the module does always warn the user about unsaved changes


Summary:	Closing the module does always warn the user about unsaved changes

Status:	RESOLVED WORKSFORME

Product:	UCS
Classification:	Unclassified
Component:	System setup
Version:	UCS 3.1
Hardware:	Other Linux

Importance:	P5 minor (vote)
Target Milestone:	UCS 3.x
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-08-21 14:17 CEST by Dirk Wiesenthal
Modified:	2018-04-14 13:37 CEST (History)
CC List:	3 users (show)

See Also:
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:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dirk Wiesenthal

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

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

2015-01-13 13:08:55 CET


*** This bug has been marked as a duplicate of bug 36700 ***

Comment 3 Alexander Kläser

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

2017-02-09 17:16:23 CET

Doesn't happen in UCS 4.2