[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: |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
||||||||||||||||||||
Issue Links: |
|
||||||||||||||||||||
Epic Link: | Zabbix 7.0 | ||||||||||||||||||||
Team: | |||||||||||||||||||||
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:
|
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: API documentation: |
Comment by Dimitri Bellini [ 2023 Jun 23 ] |
Hi DevTeam, 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 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, 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 |