[ZBX-3144] Items list is empty for templated trigger Created: 2010 Oct 26 Updated: 2017 May 30 Resolved: 2011 Feb 20 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Frontend (F) |
Affects Version/s: | 1.8.4rc2 |
Fix Version/s: | 1.8.5 |
Type: | Incident report | Priority: | Blocker |
Reporter: | Oleksii Zagorskyi | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: | item_list_for_templated_trigger_is_empty.png |
Description |
See picture - this is attempt to edit built in templated trigger. |
Comments |
Comment by richlv [ 2010 Oct 26 ] |
interesting. when creating a new trigger, if i set host to be all, i get all template items, but i can't choose templates in the host dropdown at all. quite limiting indeed. |
Comment by Oleksii Zagorskyi [ 2010 Oct 26 ] |
richlv, you write "if i set host to be all", maybe more accurately - "if i set Group to be all and Host to be all"? |
Comment by Oleksii Zagorskyi [ 2010 Nov 01 ] |
The problem with empty list is not reproducible now in trunk rev 15170. |
Comment by Alexey Fukalov [ 2010 Nov 15 ] |
dev branch: |
Comment by richlv [ 2010 Nov 15 ] |
now both comparison & trigger function parameter fields are filled in from trigger function parameter in the expression for example, {A Test Host:log[/usr/local/apache2/logs/error_log,error].str(error)}=1 gives me "error" in both of those fields |
Comment by Alexey Fukalov [ 2010 Nov 15 ] |
removed parsing of existing expression, adding expression will be always with empty\default fields |
Comment by richlv [ 2010 Nov 15 ] |
confirming the fix in dev branch rev 15505, leaving issues as is for a code review |
Comment by Alexey Fukalov [ 2010 Nov 16 ] |
branches/1.8 15510 |
Comment by Oleksii Zagorskyi [ 2010 Nov 16 ] |
Try to edit trigger: |
Comment by Oleksii Zagorskyi [ 2010 Dec 25 ] |
Additional problem: >40 |
Comment by Oleksii Zagorskyi [ 2011 Jan 04 ] |
hmm. It's bad that it will not be solved in 1.8.4 |
Comment by Alexei Vladishev [ 2011 Jan 04 ] |
We did all our best to include as many fixes into 1.8.4 as possible. I do hope we'll finally come to a much shorter release cycle for stable releases, therefore critical issues like this one will be fixed and released no longer than within a few weeks. |
Comment by Oleksii Zagorskyi [ 2011 Feb 20 ] |
I tested latest revisions of 1.8 branche and trunk. Now i see another minor bug, which i'll register as separate issue. |
Comment by richlv [ 2011 Feb 20 ] |
thanks for testing - closing then |