[ZBX-23760] Disabled action can be enabled back with broken condition expression Created: 2023 Nov 29 Updated: 2025 Nov 19 Resolved: 2025 Apr 07 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | API (A), Frontend (F), Server (S) |
| Affects Version/s: | 5.0.41rc1, 6.0.24rc1, 7.0.0alpha8 |
| Fix Version/s: | 6.0.39rc1, 7.0.10rc1, 7.2.4rc1, 7.4.0alpha1 |
| Type: | Problem report | Priority: | Critical |
| Reporter: | Edgar Akhmetshin | Assignee: | Andrejs Griščenko |
| Resolution: | Fixed | Votes: | 11 |
| Labels: | action, conditions | ||
| Remaining Estimate: | 0h | ||
| Time Spent: | 120h 35m | ||
| Original Estimate: | 0h | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Prev.Sprint, S24-W12/13, S24-W14/15, S24-W16/17, S24-W32/33, S24-W36/37, S24-W38/39, S24-W40/41, S24-W42/43, S24-W44/45, S24-W46/47, S24-W50/51/52/1, S25-W2/3, S25-W4/5, S25-W6/7, S25-W8/9, S25-W10/11, S25-W12/13 | ||||||||||||||||||||||||||||||||||||||||||||
| Story Points: | 1 | ||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Steps to reproduce:
Result: Expected: |
| Comments |
| Comment by dimir [ 2024 Feb 01 ] |
|
Related change request: ZBXNEXT-551 |
| Comment by ekorre [ 2025 Jan 30 ] |
|
Hello, you close another ticets but we still have problem in my scenario I can't go to triggers acttion. I have 500 error.
My log from nginx: |
| Comment by Everaldo Santos Cabral [ 2025 Feb 13 ] |
|
I also have the same problem when I put "any" or "disabled" in "trigger actions" and a 500 error occurs. |
| Comment by Alexander Vladishev [ 2025 Feb 13 ] |
|
everaldoscabral, Could you provide more details about your issue and how to reproduce it? What do you mean by "I put 'any' or 'disabled'"? |
| Comment by Everaldo Santos Cabral [ 2025 Feb 14 ] |
|
My scenario: zabbix-* ==> 7.0.8 Error: If I change it to "any" or "disabled" and don't put anything in the filter, it will give a 500 error.
|
| Comment by Andrejs Griščenko [ 2025 Feb 14 ] |
|
Available in:
|
| Comment by Martins Valkovskis [ 2025 Feb 26 ] |
|
Updated documentation:
Updated API changes: |