richlv
added a comment - 2010 Sep 29 15:40 item multiplier/formula is very confusing, but it should also be taken in context of xml export, where field names sometimes can be matching, and sometimes - not

Alexander Vladishev
added a comment - 2011 Feb 24 15:47 - edited All right, we have to finish this task.
Here is list of things to be done:
the branch should probably be recreated, it is just too old
items.description => items.name, items.description (text)
add support of
{ITEM.DESCRIPTION<1-9>}
GUI form for items should be changed (Description -> Name)
GUI item mass updated should be changed as well (add support for the new Description field)
Re-naming of other table fields is out of scope.

Aleksandrs Saveljevs
added a comment - 2011 Mar 31 14:59 - edited (12) It is possible to create a trigger that references an item that does not exist.
<Vedmak> FIXED
<asaveljevs> Perfect. But since we started messing with invalid trigger expressions, could you please take a look at why we have an undefined index when switching trigger expression to "
{Zabbix server: .last(0)}
=0" (note the space in place of item key).
<Vedmak> FIXED
<asaveljevs> CLOSED

Aleksandrs Saveljevs
added a comment - 2011 Mar 31 15:00 - edited (13) It is possible to create a trigger that references a discovery rule. If we then click on that discovery rule in the trigger expression, we get no permissions error.
<Vedmak> it's not connected to this issue
<asaveljevs> Moved to ZBX-3674 . CLOSED

Aleksandrs Saveljevs
added a comment - 2011 Apr 05 17:14 - edited (16) [API] Should rename "description" to "name" on http://www.zabbix.com/documentation/2.0/manual/appendix/api/item/get . The examples with "description" are probably still valid, but they are not as natural anymore.
<Vedmak> changed, but as mentioned, it was valid
<asaveljevs> I have also renamed "description" to "name" in "sortfield" row. If you like it, please close this comment and merge the branch.
<Vedmak> Like it, CLOSED