-
Change Request
-
Resolution: Unresolved
-
Trivial
-
None
-
5.4.5
-
None
-
probably does not matter
Steps to reproduce:
- Configuration > Services
- configure some service with trigger bound from selected host
- see it back in Configurattion > Services
Result:
host is identified in individual service configuration form, but not in whole service tree configuration
Expected:
host indentified in both places to improve readability, to be able much more efficiently check the configuration, see e.g. Elasticsearch cluster here:
I know, that all this functionality is going to be improved in 6.0, but I still hope, that such a small thing as described in this FR, could be added also in 5.4.6