Closed icinga-migration closed 6 years ago
Updated by Konne on 2016-03-18 06:58:24 +00:00
When auto-grouping is disabled as described above, the first sort also activates grouping for the respective field. When I disable grouping for this field, all further sorts won't activate grouping again.
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11405
Created by Konne on 2016-03-17 19:05:09 +00:00
Assignee: (none) Status: New Target Version: (none) Last Update: 2016-03-18 06:58:24 +00:00 (in Redmine)
Hello,
we are using own grid-based views and the grouping-feature in our environment. Today i observed the following bug:
The grouping-parameter "field" does not work at all (see figure 2.5): https://wiki.icinga.org/display/Dev/Using+templates+to+write+your+own+grid+based+views#Usingtemplatestowriteyourowngridbasedviews-2.5The%3Cgrouping%3Eseection
When grouping-parameter "enabled" is activated (even without the "field"-parameter defined at all), the corosponding baseview is always grouped by the first field as defined within the template, which has the order-parameter "default" activated. I tested this with different fields (with and without the grouping-parameter "field" defined) and it is reproducible.
In its activated default state, all hosts are getting grouped by the field "host_id" (the first field with default order = true), which is rather annoying. As a workaround, i deactivated the order-parameter "default" for all fields. The default-grouping by the first field with default order = true is gone, but the alphabetical default order too :~
Is it possible to activate the grouping-feature for a template, but without being forced to define a grouping-field? Grouping is nice, but being forced to use it always is a bit too much ;-) Is this maybe connected with the bug?
Greetings from nuremberg