Bug 32588 – Saving changes in [Options] not always possible on first try

Bug 32588 - Saving changes in [Options] not always possible on first try


Summary:	Saving changes in [Options] not always possible on first try

Status:	RESOLVED WORKSFORME

Product:	UCS
Classification:	Unclassified
Component:	UMC - Computers
Version:	UNSTABLE
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 3.2-x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-09-13 11:25 CEST by Timo Denissen
Modified:	2019-01-07 15:05 CET (History)
CC List:	5 users (show)

See Also:	25240
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?:	Yes
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 Timo Denissen

2013-09-13 11:25:02 CEST

Seen when editing a IP managed client:

When editing in the UMC, removing "Nagios support" in [Options] and then trying to save, the UMC shows three different behaviors:

1. Saving the change and returning to the overview
2. Not reacting at all, after several clicks on "Save changes" gives the message "No changes have been made."
3. Directly the message "No changes have been made."

Saving does not always work on first try. The behavihor is reproduceable.

Comment 1 Timo Denissen

2013-09-20 08:59:29 CEST

I just observed the behaviour when editing a Windows computer object. After making changes the "Save changes" button does nothing. After closing, re-opening and re-editing savong works as expected.

Comment 2 Florian Best

2013-09-20 09:17:06 CEST

→ Bug #25240

Comment 3 Florian Best

2017-06-28 14:53:05 CEST

There is a Customer ID set so I set the flag "Enterprise Customer affected".

Comment 4 Florian Best

2017-10-12 19:05:09 CEST

@Timo: still reproducible?

Comment 5 Stefan Gohmann

2019-01-03 07:30:39 CET

This issue has been filed against the UCS version "unstable" which does not really exist. Please change the version value.

Comment 6 Andreas Peichert

2019-01-07 15:02:47 CET

@Timo: "worksforme" as discussed