ZBXNEXT-4358 has no (26).

this was edited - but ZBXNEXT-4359 still has no (26)

gcalenko Thank you, fixed issue description.

<richlv> ...it now references ZBXNEXT-4359, but that issue has no escaping problems mentioned.

for a casual onlooker - zabbix team has closed up and comments on issues from the team are secret now. the guess is that in ZBXNEXT-4359 there is a comment about this problem, just that nobody but the developers can see it.

my personal take is that this approach is detrimental for zabbix long-term. it is unlikely to change, though. nothing much can be done for this particular issue.

Hey, richlv, you should know that there is no equality between company's policy and employee's personal opinion. Typically employee cannot even afford such. Your comments here are not watched by those who can change the policy and may only lead to employees' desire to create tickets with restricted access instead of public ones to avoid such discussions. Be certain that company's current policy will not object that.

glebs.ivanovskis, a very valid point. please let me reassure everybody that the intent has never been to stifle individual developers. quite the opposite, the effort of all the great individuals is highly appreciated. perhaps other communication channels are to be considered for such feedback.

Fixed in scope of ZBX-22386.