[ZBXNEXT-2299] Extended filter to work with acknowledged problems Created: 2014 May 15  Updated: 2024 Jun 27  Resolved: 2023 Jun 09

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F)
Affects Version/s: 2.2.3, 6.0.10, 6.2.4
Fix Version/s: 7.0.0alpha2, 7.0 (plan)

Type: Change Request Priority: Minor
Reporter: richlv Assignee: Miks Kronkalns
Resolution: Fixed Votes: 8
Labels: acknowledges, filters, triggers
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot from 2023-06-23 18-25-10-1.png     PNG File Screenshot from 2023-06-23 18-25-10-2.png     PNG File Screenshot from 2023-06-23 18-25-10.png     PNG File Screenshot from 2023-06-23 18-25-21.png     PNG File acknowledgement-status.png     PNG File image-2023-05-19-10-17-31-386.png     PNG File image-2023-05-19-10-19-43-771.png     PNG File message.png     PNG File screenshot-1.png    
Issue Links:
Duplicate
is duplicated by ZBXNEXT-4337 Zabbix "Problems" Dashboard widget - ... Closed
is duplicated by ZBXNEXT-6418 filter support by acknowledged incidents Closed
is duplicated by ZBXNEXT-4251 Widget has only the option of "Show u... Closed
Sub-task
Epic Link: Zabbix 7.0
Team: Team B
Sprint: Sprint 99 (Apr 2023), Sprint 100 (May 2023), Sprint 101 (Jun 2023)
Story Points: 3

 Description   

Customer desires a more restricted filtering option of problems acknowledged by the current user that is using the frontend. The end result can be imagined as a drop down menu of the following options:

  • Any problems
  • Unacknowledged problems only
  • Acknowledged problems only
  • Problems acknowledged by me only


 Comments   
Comment by Miks Kronkalns [ 2023 May 02 ]

Implemented in development branch feature/ZBXNEXT-2299-6.5.

Comment by Dace Petra (Inactive) [ 2023 May 25 ]

Implemented in 7.0.0alpha2 (master) d01112d71cd

Comment by Romans Novarro (Inactive) [ 2023 May 31 ]

Documentation updated:

User manual: 
Monitoring - Problems
Widgets - Problems
 Page parameters
What's new in Zabbix 7.0.0

API documentation:
Widget fields - Problems
event.get documentation
problem.get documentation
Changes from 6.4 to 7.0

Comment by Dimitri Bellini [ 2023 Jun 23 ]

Hi DevTeam,
I do not know if it's the right place to discuss it but the new filter option of "Acknowledeg" could be a nice addiction if it's also clear where we need to "Acknowledeg" a problem.
On Zabbix 7.0 Alpha2 the old link for "Ack" it's change in "update", for a new user I think it's not so intuitive.

Also, on the "Update" modal view everything it's "flatted" and it's not so easy to find the "Acknowledeg" option.

Could be nice to see some Highlight for the most important features on this specific modal view.

Thanks so much

Comment by Alex Kalimulin [ 2023 Jun 26 ]

dimitri.bellini, the Update button was added in 6.4 with the purpose of making the UI easier and more accessible for new users (see ZBXNEXT-7605). It was difficult to explain that the user needed to press Ack to change the severity or suppress the problem. The current pattern, I believe, resolved the long-standing UI inconsistency that seemed natural to old-timers but was confusing to everyone else.

And while I agree that Acknowledge is important for the workflow, we don't have a common UI pattern that visualizes the degree of importance. If we ever introduce such a notion, this should be utilized across the entire UI. But we should be careful with such patterns because promoting our opinionated feature importance rankings to users with contradicting habits can provoke some unnecessary debates or more confusion.

Comment by Dimitri Bellini [ 2023 Jun 26 ]

Hi Alex,
and thanks for the feedback.
My consideration it comes from as you already mention "long-standing UI inconsistency" and in this specific case the introduction of the filter for "Ack" it's a step forward for more "inconsistency"

How a new user is able to correlate "Ack" with "Update"?

I would suggest to start to think about to "UI pattern that visualizes the degree of importance", at least a first implementation.

Thanks so much

Generated at Sat Apr 19 12:28:51 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.