Is there a way to let Zammad close tickets, when the Monitoring state changes from CRITICAL to WARNING? We do not want to handle WARNING “issues”, only CRITICAL issues via Zammad.
Maybe there’s a possible workaround via /opt/zammad/app/models/channel/filter/monitoring_base.rb?
BTW, i am using the Icinga-Integration.
The message-Body looks like this:
Well actually the Trigger-Option is the best approach you can use I think.
Reason behind this is, that everything else would involve code changes which are not update safe and need to be redone after every update.
I also don’t think that this will find it’s way into Zammad-default, as this seems to be a rather specific use-case… at least not in the way you would do it. (I mean in terms in fiddling around with the code to make it wqork the way you need it to).
Should be the file you’d need to edit, but again, it’s fiddling.