[ZBXNEXT-4823] Ack screen doesn't acknowledge by default Created: 2018 Oct 18 Updated: 2024 Jan 26 Resolved: 2024 Jan 26 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Frontend (F) |
Affects Version/s: | 4.0.0 |
Fix Version/s: | None |
Type: | Change Request | Priority: | Trivial |
Reporter: | Craig Hopkins | Assignee: | Alexei Vladishev |
Resolution: | Won't fix | Votes: | 2 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
On the dashboard, if I click on "No" next to a problem, the screen doesn't have "Acknowledge" ticked by default, therefore it's just a comment. As the page is to "Update problem", the column should either be "Comment" rather than "Ack" or "Acknowledge" should be ticked by default. |
Comments |
Comment by Edgars Melveris [ 2018 Oct 22 ] |
This is correct, but i'm not sure this is a bug. Looks more like a feature request.
|
Comment by Edgars Melveris [ 2018 Oct 22 ] |
In version 3.4 there was no checkbox for acknowledge, so you can say, that it was always checked, without possibility to uncheck. Now that the option exists, maybe it should be the default to have it checked. |
Comment by Nicola Mauri [ 2019 Jan 07 ] |
I confirm this. After upgrading to 4.0, our users keep forgetting to select the "ack" checkbox (as it wasn't necessary in previous versions), so the problem does not get acknowledged and the escalation workflow does not work anymore. Users click on the "ack" column in problem page, so they expect to just ack... and honestly I can't blame them. Probably the "ack" checkbox should be checked by default or a config option should be provided to allow administrators to set the desiderated default behaviour. |
Comment by Craig Hopkins [ 2019 May 31 ] |
Still affecting 4.2.2 |
Comment by Nicola Mauri [ 2019 May 31 ] |
As a (very) dirty hack, you may edit "app/views/monitoring.acknowledge.edit.php" and change: |
Comment by Craig Hopkins [ 2024 Jan 26 ] |
This can be closed now, because 6.4 has changed the text to "Update" |