Univention Bugzilla – Bug 42756
Class sorting in User(schools) module grid wrong
Last modified: 2017-06-23 13:32:25 CEST
Reported by customer and reproducible. The customer can't sort User in the User(schools) module as he expect. E.g. He has students in the class 5_a, 5_b ... - ...,10_e, 10_f. If he try to sort the header "Klasse" ascending the sorting is something like: 5_a 5_c 5_a 5_e ... Seems like a bug to me and a incorrect sorting is reproducible in my test environment.
I guess the sorting is done with the school prefix.
(In reply to Florian Best from comment #1) > I guess the sorting is done with the school prefix. May the case but shouldn't affect the sorting. The school is already selected and all students have the same school prefix.
Reported again by a customer I found, that using "formatter" in "schoolwizards.UserGrid" for "school_classes" is the cause: It seems that the grid tries to sort by the stored Objects, but not by the formatted values. The dojo documentation suggests "to transform the data before it gets to your store" http://dojotoolkit.org/documentation/tutorials/1.10/populating_datagrid/
(In reply to Andreas Peichert from comment #3) > Reported again by a customer Which UCS@school version? 4.2?
(In reply to Florian Best from comment #4) > (In reply to Andreas Peichert from comment #3) > > Reported again by a customer > Which UCS@school version? 4.2? 4.1 R2 v10
Created attachment 8812 [details] customer screenshoot
Created attachment 8813 [details] customer screenshoot
r79561: fix class sorting in User(schools) module r79563: changelog r79564: YAML Package: ucs-school-umc-wizards Version: 9.0.5-2A~4.2.0.201705231352 Branch: ucs_4.2-0 Scope: ucs-school-4.2 This fix can't easily be back-ported to 4.1, because we changed the grid library. Please clone this bug if this is needed for 4.1 as well.
r79621: changed sortRepresentation to sortFormatter
OK: sorting works nice again!
UCS@school 4.2 v2 has been released. http://docs.software-univention.de/changelog-ucsschool-4.2v2-de.html If this error occurs again, please clone this bug.