Bug 28198 - MultiSelect: click on name unchecks other components
MultiSelect: click on name unchecks other components
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: UMC (Generic)
UCS 3.0
Other Linux
: P3 normal (vote)
: UCS 3.1
Assigned To: Florian Best
Dirk Wiesenthal
: interim-3
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-13 15:41 CEST by Felix Herrmann
Modified: 2012-12-12 21:07 CET (History)
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):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Herrmann univentionstaff 2012-08-13 15:41:01 CEST
A click on a component name in the software settings module in appliance mode  unchecks all previously/automatically checked components. The resulting system  is not fully/not correct configured. 

This behaviour should be changed to: click on a component name changes only the checkbox of this component (as it is when clicking the checkbox of the component).
Comment 1 Alexander Kläser univentionstaff 2012-08-14 10:33:31 CEST
Yes, for the usability, it would be better to change the default behaviour. This affects also other Widgets (see Bug 24388).
Comment 2 Florian Best univentionstaff 2012-09-07 14:01:23 CEST
In Dojo1.8 only the checkboxes on the left are clickable.
Comment 3 Dirk Wiesenthal univentionstaff 2012-09-13 14:14:56 CEST
We should consider reimplementing it the way we want (i.e. that clicking on a row does not uncheck the previous selection). Now it is a loss of functionality.

As this may be complicated, tagging it interim-3
Comment 4 Alexander Kläser univentionstaff 2012-09-14 12:58:06 CEST
(In reply to comment #3)
> We should consider reimplementing it the way we want (i.e. that clicking on a
> row does not uncheck the previous selection). Now it is a loss of
> functionality.

Yes, in case we need the old functionality, we should do that and open a new bug. For now IMHO, this bug can be marked as RESOLVED.

*** This bug has been marked as a duplicate of bug 26857 ***
Comment 5 Dirk Wiesenthal univentionstaff 2012-11-13 10:27:35 CET
(In reply to comment #4)
> Yes, in case we need the old functionality, we should do that and open a new
> bug. For now IMHO, this bug can be marked as RESOLVED.

Agreed. But this change is worth a changelog entry.
Comment 6 Stefan Gohmann univentionstaff 2012-11-15 06:51:53 CET
I've added a changelog entry.
Comment 7 Dirk Wiesenthal univentionstaff 2012-11-15 12:51:27 CET
VERIFIED
Comment 8 Stefan Gohmann univentionstaff 2012-12-12 21:07:49 CET
UCS 3.1-0 has been released: 
 http://forum.univention.de/viewtopic.php?f=54&t=2125

If this error occurs again, please use "Clone This Bug".