Creating an item that performs something (ping, port check etc...) using the '{HOST.CONN}' built in macro would be nice to use in the item name.

For example we sometimes ping multiple addresses on a host and we have triggers that user user macros in the name and they get resolved, however {HOST.CONN} does not.

User Macros:

{$DEVICE_IP.ADSL_LINK} = "1.1.1.1"
{$DEVICE_IP.NBN_LINK} = "2.2.2.2"
{$DEVICE_IP.MGMT} = "3.3.3.3"

Item Name Defined:

ICMP Ping - Ping Response (ADSL Link:{$DEVICE_IP.ADSL_LINK})
ICMP Ping - Ping Response (NBN Link:{$DEVICE_IP.NBN_LINK})
ICMP Ping - Ping Response (Management Interface:{$DEVICE_IP.MGMT})
ICMP Ping - Ping Response (Management Interface:{HOST.CONN})

Item Name Displayed in latest data:

ICMP Ping - Ping Response (ADSL Link:1.1.1.1)
ICMP Ping - Ping Response (NBN Link:2.2.2.2)
ICMP Ping - Ping Response (Management Interface:3.3.3.3)
ICMP Ping - Ping Response (Management Interface:{HOST.CONN})

Notice how {HOST.CONN} does not expand, however it does in the key name as per documentation.

Really useful for the support engineers to see built in and user macros data in item names.

NOTE: I have an open feature request ZBXNEXT-7497 to revert the removal of user macros from items names performance by ZBXNEXT-7115. This is because sometimes things are not static and can change which is where user macros are extremely useful.