[ZBXNEXT-4415] Display one problem per line in Problems view (Z4) Created: 2018 Mar 08  Updated: 2024 Apr 10  Resolved: 2018 May 22

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F)
Affects Version/s: None
Fix Version/s: 4.0.0alpha6, 4.0 (plan)

Type: Change Request Priority: Trivial
Reporter: Rostislav Palivoda Assignee: Andrejs Griščenko
Resolution: Fixed Votes: 1
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PNG File Selection_428.png     PNG File Selection_434.png     PNG File Selection_435.png     PNG File incorrect-border-color-between-severities-hc-dark.png     PNG File incorrect-border-color-between-severities-hc-light.png     PNG File incorrect-border-color-between-severities.png     PNG File incorrect-displaying-of-second-column.png     PNG File second-ellipsis.png    
Sub-Tasks:
Key
Summary
Type
Status
Assignee
ZBXNEXT-4526 Improve Problems compact view - tags ... Change Request (Sub-task) Closed Andrejs Griščenko  
Team: Team B
Sprint: Sprint 29, Sprint 30, Sprint 31, Sprint 32, Sprint 33, Sprint 34
Story Points: 4.5

 Description   

Monitoring?Problems must support a new mode for displaying information in a much more condensed view:

  • One problem must use no more than one horizontal row
  • At least 50 problems (more is better) must be displayed on a screen having resolution of 1920x1200, ratio 16:10.
  • If problem name is too long, it must be shortened with ability to see full problem name on mouse-over
  • A new filter option "Highlight full line [X]" (off by default) will specify if a whole problem row will be highlighted with the color of problem severity. In this case we may lose some text colors, because background color and color of text might be the same. Therefore it may happen that all text in this case will be black and white.


 Comments   
Comment by Nicola Mauri [ 2018 Mar 08 ]

I think that option to "Highlight full line" could be best fit in Zabbix GUI configuration file (zabbix.conf.php) instead of adding it in filter section.

Comment by Marek Konecny [ 2018 Mar 28 ]

Hi Nicola,

Zabbix server can be used by tens or hundreds of users and each has a different view of the optimal presentation of information. Zabbix in this direction does not provide much and every new feature is appreciated and belongs to the GUI rather than to a configuration file.

Comment by Andrejs Griščenko [ 2018 Apr 16 ]

(1) [F] New translation strings:

  • Compact view
  • Show timeline
  • Highlight whole row

sasha CLOSED

Comment by Andrejs Griščenko [ 2018 Apr 16 ]

Implemented in development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-4415

Comment by Andrejs Griščenko [ 2018 Apr 24 ]

Implemented in 4.0.0alpha6 (trunk) r80121.

Comment by Nicola Mauri [ 2018 May 25 ]

Hi Marek,

I agree with you: every GUI new feature is really appreciated by zabbix users. However I wouldn't add too much options in filters, as they add complexity and can be confusing for new users.

In this case, I don't see the benefit of being able to adjust view preferences  each time we filter results. IMHO, this kind of settings ("compact view" and "highlight full row") should be set once, for example, in user preferences. 

Comment by Marek Konecny [ 2018 May 25 ]

Hi Nicola,

Of course, User preferences is an alternative, but certainly not a config file that you mentioned.

However, The options for filtering and presenting problems are still very simple from the point of view of the end user and its ability to customize the GUI according to the user's needs must be constantly enriched.

Zabbix 4.0 in this area brings important improvements and the guys from Zabbix have to be praised for it.

Comment by Nicola Mauri [ 2018 May 25 ]

Definitely, we all are immensely grateful to Zabbix developers for the great work they are doing! I was just sharing my very personal point of view, if that can help to improve usability. Greetings!

Generated at Thu Apr 25 12:40:23 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.