-
Problem report
-
Resolution: Fixed
-
Minor
-
4.0.1
-
CentOS 7.5 , Apache HTTPD, Zabbix Frontend 4.0.1
-
Sprint 56 (Sep 2019), Sprint 57 (Oct 2019), Sprint 58 (Nov 2019), Sprint 59 (Dec 2019), Sprint 60 (Jan 2020), Sprint 61 (Feb 2020), Sprint 62 (Mar 2020)
-
1
Steps to reproduce:
- Create the Host group for Templates with the name Custom templates and Host group for the host with the name File servers
- Create a host, for example - NextCloud 13
- Create two templates, one with the name Custom Template App Zabbix Agent
- Add a few Triggers into each of the Templates
- Navigate to availability report, select:
- Mode: By trigger template
- Template group: Custom Templates
- Template : Custom Template App Zabbix Agent
- Template trigger: all
- Host group: File servers
Result:
In the filtered out result, you are able to find not only the triggers from the Custom Template App Zabbix Agent but also from the second template, however, in the filtering, there is a clear statement to show only the triggers from Custom Template App Zabbix Agent
Expected:
Expected to respect all the filtering options.
Screenshots in the attachment