Icinga / icinga-reports

Icinga Reports 1.x MySQL (EOL 31.12.2018)
GNU General Public License v2.0
14 stars 13 forks source link

[dev.icinga.com #3747] sort order of input controls for services #51

Closed icinga-migration closed 11 years ago

icinga-migration commented 11 years ago

This issue has been migrated from Redmine: https://dev.icinga.com/issues/3747

Created by mfriedrich on 2013-03-03 19:25:34 +00:00

Assignee: berk Status: Resolved (closed on 2013-04-10 15:30:16 +00:00) Target Version: 1.9 Last Update: 2013-04-10 15:30:16 +00:00 (in Redmine)


currently, the input controls are not sorted - or not in a way someone would expect it to be.

this matches for the services mostly, as you'll get the {hostalias} - {servicdesc} string only, and may scroll and scroll, but there's no sort order available.

imho, it would be good to add that to the queries - e.g. sort by hostname, and then servicedesc. though this will add some more complexity to the queries, it will add a little more comfort for the user.


Relations:

icinga-migration commented 11 years ago

Updated by berk on 2013-04-10 08:41:06 +00:00

icinga-migration commented 11 years ago

Updated by berk on 2013-04-10 12:28:04 +00:00

fixed in package

select service_object_id, concat(icinga_hosts.display_name, ' - ', icinga_services.display_name) as name from icinga_services, icinga_hosts where icinga_services.host_object_id = icinga_hosts.host_object_id order by name

icinga-migration commented 11 years ago

Updated by mfriedrich on 2013-04-10 14:52:42 +00:00

where?

besides, it is imho wrong to use alias / display_name. the reports should offer the host_name/service_description - unless someone opts for the display_name (i guess we can do that with icinga2 having that clear path).

icinga-migration commented 11 years ago

Updated by berk on 2013-04-10 15:30:16 +00:00

but Display is equal to classic for now.