[ZBX-7341] inconsistent entity selection Created: 2013 Nov 12  Updated: 2024 Apr 10  Resolved: 2019 Oct 28

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 2.2.0
Fix Version/s: 4.4.0beta1, 4.4 (plan)

Type: Problem report Priority: Major
Reporter: richlv Assignee: Roberts Lataria (Inactive)
Resolution: Fixed Votes: 10
Labels: usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File after.png     PNG File before.png    
Issue Links:
Causes
causes ZBXNEXT-5473 Template linkage - return multiselect... Closed
causes ZBX-16753 Link new templates field missing Closed
Duplicate
is duplicated by ZBX-9983 zabbix-3.0.0alpha4-56280 -- Adding mu... Closed
Epic Link: Change subforms with add buttons to popups
Team: Team D
Team: Team D
Sprint: Sprint 56 (Sep 2019), Sprint 57 (Oct 2019)
Story Points: 1

 Description   

the way new selection works is not consistent and highly confusing to users. consider these two examples :

a) in the dashboard filter, adding groups happens just by adding them to a field. they are removed with "X" next to each 'floating block'
b) in template linking tab, templates are added the same way as in (a)... but then user also has to click on 'add' link and templates are removed by clicking on "unlink".

to make things worse, template mass update does not require that extra "add" step.

places where this should be changed :
1) template linkage in host/template properties
2) template selection for action conditions (network discovery, autoreg)
3) templates tab in host prototypes
4) more ?

instead, in the second case, new templates should be just added to this new control and "add" control should be removed completely. special case handling for just added templates (not showing "unlink & clear") probably can be nuked, too.

all places where the new controls are used should be reviewed.

filing as a bug because of the huge confusion this causes to users after they use one and another way in different locations



 Comments   
Comment by robert pearce [ 2016 Feb 15 ]

+1, this bug is super confusing and has caught me out several times just in the last 2 days of using zabbix.

Comment by richlv [ 2016 Mar 14 ]

this seems to be the top usability issue in zabbix for many years. just now from irc :

<modem_> I am trying to link Template to my second zabbix host but it won't work, I mean the "select" and "add" function won't add anything, and no error neither
<volter> modem_: Did you click the "Add" link?
<modem_> This is working Thanks a lot
<lamba> modem_: that trips me up once a week, every week.

Comment by Volker Fröhlich [ 2016 Mar 24 ]

The dialogs for copying entities and trigger dependency are different too. The later is super-annoying to use, as it keeps forgetting everything.

Comment by dimir [ 2019 Sep 12 ]

A couple of screenshots "before" and "after" would be great. And at least some explanation of what has been done.

Comment by Roberts Lataria (Inactive) [ 2019 Sep 12 ]

dimir, removed multiselect. Now used popup. By analogy how in triggers dependencies.
Before:

After:

Comment by dimir [ 2019 Sep 12 ]

rlataria, great! Thanks a lot!

Comment by Roberts Lataria (Inactive) [ 2019 Sep 25 ]

Fixed in:

Comment by Arli [ 2019 Oct 12 ]

I'm sad to see the "type here to search" feature gone  It was way easier and quicker to search than browse.

Comment by Jens Friedrichs [ 2019 Oct 15 ]

As Arli sad ... the "type here to search" feature is missing in the new popup  

Comment by Valdis Murzins [ 2019 Oct 15 ]

I would suggest you to put a vote on this task: ZBXNEXT-5473

Comment by Martins Valkovskis [ 2019 Oct 16 ]

Just to recap:

  • We added a multiselect field for template linking in 2.2 (many multiselects were gradually added starting with that version)
  • This ticket asked to remove the extra 'Add' step (inconsistent with other multiselect fields)
  • We removed the multiselect field instead, effectively going back to a pre-2.2 state
  • Now we are dealing with another ticket asking to put a something like a multi-select back (ZBXNEXT-5473), even though we just removed it ourselves

Heeelp! The logic here is getting hard to follow.

On top of that the mass update still has a multiselect field and the "type here to search" string. Although the "typing to search" seems to work no more, for template mass update (works for host mass update).

Comment by Ingus Vilnis [ 2019 Oct 16 ]

Why did you guys implement it this way? Please enlighten why yet another UX regression is added by requiring more clicks to already crippled template linking since removal of twin boxes?

You pushed so hard to add assistive technologies and keyboard navigation to 4.0. Now try linking a template in 4.4 just with the keyboard. 

And you can't add/remove hosts from the template in Configuration -> Templates section either, which is particularly annoying when developing new templates. The number of extra steps required for linkage is immense. And no, don't even try mentioning mass update here, as it still is complicated if you can't have all hosts in one filter selection for the update operation.

However, you can't annoy your users more than asking for votes on a feature which you broke on purpose and then make users wait forever because see the feature request has not enough votes to bring it on the radar. 

Comment by Rostislav Palivoda [ 2019 Oct 18 ]

Please follow on ZBXNEXT-5473

Comment by Alexander Vladishev [ 2019 Oct 28 ]

Updated documentation:

Generated at Sat Apr 20 16:31:26 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.