|
Causes |
|||
| caused by |
|
Ability to search problems by trigger... | Closed |
Team A
[ZBX-15129] dbupgrade does not replace {TRIGGER.NAME} to {EVENT.NAME} Created: 2018 Nov 06 Updated: 2024 Apr 10 Resolved: 2018 Nov 21 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 4.0.1 |
| Fix Version/s: | 4.0.2rc1, 4.2.0alpha1, 4.2 (plan) |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Kodai Terashima | Assignee: | Andris Zeila |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Team: | Team A |
||||||||
| Sprint: | Sprint 46, Nov 2018 | ||||||||
| Story Points: | 1 | ||||||||
| Description |
|
According to documentation, {TRIGGER.NAME} is replaced by {EVENT.NAME} while database upgrade.https://www.zabbix.com/documentation/4.0/manual/installation/upgrade_notes_400 {TRIGGER.NAME} is replaced by {EVENT.NAME}in all trigger-based actions when upgrading. Zabbix 4.0.0 and 4.0.1 do not change the macro while upgrading from 3.0. |
| Comments |
| Comment by Andris Zeila [ 2018 Nov 16 ] |
|
Released in:
|