(3) according to (2),
support was also added in trigger name/description, but there is no changelog entry on that
Documentation also should be updated
Andris Zeila updated changelog in pre-2.2.2rc1 r42007 and pre-2.3.0 r42008
Andris Zeila marked as supported in overview and added 'supported since' note https://www.zabbix.com/documentation/2.2/manual/appendix/macros/supported_by_location?&#overview
Andris Zeila and updated whatsnew https://www.zabbix.com/documentation/2.2/manual/introduction/whatsnew222?&#daemon_improvements
Aleksandrs Saveljevs Fixed typo in changelog entry in r42090.
Aleksandrs Saveljevs In https://www.zabbix.com/documentation/2.2/manual/appendix/macros/supported_by_location , I think that "internal and trigger" is a more suitable style for official documentation than "internal/trigger". Simiarly for "names/descriptions".
Aleksandrs Saveljevs In "What's new", the change is only listed as a daemon improvement, but it also an improvement in the frontend. REOPENED.
Andris Zeila Removed '/' from HOST.PORT macro description. Similar style was already used there, so I though it's acceptable. Regarding frontend documentation - I'm passing that to Oleg.
Oleg Egorov RESOLVED
<richlv> now we have footnote "Supported since 2.2.2." and in the description "Supported in trigger names and descriptions since 2.2.2.".
other entries have various combinations of this, too. let's agree on some guidelines and unify this.
Martins Valkovskis I'd propose the general rule as this - 'supported since' comments go in the Description (as done originally). However, when 'supported since' comments include a long listing (or would have to be repeated in too many cells), it is acceptable to add them in the footnotes and link to them.
Martins Valkovskis Also, reviewed and removed the 'supported since' duplication in this particular case. And, for 'what's new', reviewed and improved the wording a bit and split it out into 'macro improvements' separately, rather than in 'daemon improvements'. Seeing that developer review of doc content has already taken place, I will set this as CLOSED.