[ZBX-12082] Impossible to select triggers with same name in multiselect Created: 2017 Apr 20  Updated: 2024 Apr 10  Resolved: 2017 Nov 12

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 3.2.7, 3.4.0alpha1
Fix Version/s: 3.2.11rc1, 3.4.5rc1, 4.0.0alpha1, 4.0 (plan)

Type: Problem report Priority: Minor
Reporter: Ivo Kurzemnieks Assignee: Ivo Kurzemnieks
Resolution: Fixed Votes: 0
Labels: multiselect, triggers
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File broken-scrolling.png    
Team: Team B
Team: Team B
Sprint: Sprint 16, Sprint 17, Sprint 18, Sprint 19, Sprint 20
Story Points: 1

 Description   

Triggers can have same names, but different expressions. If chosen such triggers from popup window, only one trigger remains in multiselect input field.

 Comments   
Comment by Kim Jongkwon [ 2017 Aug 31 ]

I confirmed this multiselect problem on below:
Zabbix Version : 3.2.2 ~ 3.2.7 and 3.4.1

  • Monitoring -> Problems -> Filter:Triggers popup
  • Configuration -> Actions -> New condition:Trigger select popup

This issue occurred from Zabbix 3.2.2. (No problem with 3.2.1)

Comment by Rostislav Palivoda [ 2017 Sep 04 ]

Workaround - select trigger from a popup window.

Comment by Ivo Kurzemnieks [ 2017 Oct 31 ]

(1) No translation string changes.

vmurzins CLOSED

Comment by Ivo Kurzemnieks [ 2017 Oct 31 ]

(2) Fixed the issue with inconsistent data passing (ZBX-12083) r74144

sasha CLOSED

Comment by Ivo Kurzemnieks [ 2017 Oct 31 ]

RESOLVED in svn://svn.zabbix.com/branches/dev/ZBX-12082 r74137

Comment by Ivo Kurzemnieks [ 2017 Nov 10 ]

Fixed in:

  • pre-3.2.11rc1 r74466
  • pre-3.4.5rc1 r74468
  • pre-4.0.0alpha1 (trunk) r74469
Generated at Sat Apr 20 08:18:49 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.