Function last(0) in a trigger

[gbmadmin]

I have some default triggers that are configured with a "last(0)" function, just like:

{Template OS Linux:vm.memory.size[available].last(0)}<20M

If I try to change the triggering value, I get an error whenever I leave zero in the "Last of T field". I can put "0s", or "#1", but I cannot leave the "0" value, and a "#0" is not accepted as well. Even when I don't change anything, I have to clear the field and the expression changes from

{Template OS Linux:vm.memory.size[available].last(0)}<20M

to

{Template OS Linux:vm.memory.size[available].last()}<20M

Maybe the "last()" part of the expression works the same as "last(0)", but it's a bit annoying not being able to set the previous expression value, because it makes you think there's an error somewhere.

IMHO, Zabbix should accept a "#0" value, or show "last()" instead of last(0) as default.

[Semiadmin]

last(0) is an outdated syntax from v1.*. It deprecated but still supported. Current syntax is last() or last(#1).

[gbmadmin]

Great news, thanks.

May I suggest that you get silently rid of the 0 in the editing field, so to avoid the error? See pictures.