[Bug]: Notifications not working after Upgrading to Version 0.1.1-1.bookworm

[citfs]

Please try to fill out as much of the information below as you can. Thank you!

• Yes, I've searched similar issues on GitHub and didn't find any.

Which version contains the bug?

0.1.1-1.bookworm

Describe the bug

After upgrading the Version to 0.1.1-1.bookworm via the Netways Package Repository our Zammad Notifications the notifications to Zammad are not working.
In the Icinga debug log i can see the following error:
"[UNKNOWN] - unable to parse search results: json: cannot unmarshal array into Go value of type zammad.TicketSearchResult (*fmt.wrapError)"

Output of icinga2 debug Log:
[2025-04-28 09:39:47 +0200] debug/Notification: User 'zammad' notification 'host.name!apt-updates!Notify Service (Zammad)', Type 'Custom', TypeFilter: Acknowledgement, Custom, DowntimeEnd, DowntimeRemoved, DowntimeStart, Problem and Recovery (FType=8, TypeFilter=123) [2025-04-28 09:39:47 +0200] debug/Notification: User 'zammad' notification 'host.name!apt-updates!Notify Service (Zammad)', State 'Critical', StateFilter: Critical, Down, OK, Unknown, Up and Warning (FState=4, StateFilter=63) [2025-04-28 09:39:47 +0200] information/Notification: Sending 'Custom' notification 'host.name!apt-updates!Notify Service (Zammad)' for user 'zammad' [2025-04-28 09:39:47 +0200] notice/Process: Running command '/usr/lib/nagios/plugins/notify_zammad' '--check-output' 'APT CRITICAL: 3 packages available for upgrade (3 critical updates). linux-libc-dev (security)' '--check-state' 'CRITICAL' '--host-name' 'host.name' '--notification-type' 'CUSTOM' '--secure' '--service-name' 'apt-updates' '--token' 'XXX' '--zammad-customer' 'svc_icinga_mail' '--zammad-group' '0 - Dispatching' '--zammad-hostname' 'support.xx.xxx' '--zammad-port' '443': PID 1492056 [2025-04-28 09:39:47 +0200] information/Notification: Completed sending 'Custom' notification 'host.name!apt-updates!Notify Service (Zammad)' for checkable 'host.name!apt-updates' and user 'zammad' using command 'notify_zammad'. [2025-04-28 09:39:47 +0200] notice/Process: PID 1492056 ('/usr/lib/nagios/plugins/notify_zammad' '--check-output' 'APT CRITICAL: 3 packages available for upgrade (3 critical updates). linux-libc-dev (security)' '--check-state' 'CRITICAL' '--host-name' 'host.name' '--notification-type' 'CUSTOM' '--secure' '--service-name' 'apt-updates' '--token' 'XXX' '--zammad-customer' 'svc_icinga_mail' '--zammad-group' '0 - Dispatching' '--zammad-hostname' 'support.xx.xxx' '--zammad-port' '443') terminated with exit code 3 [2025-04-28 09:39:47 +0200] warning/PluginNotificationTask: Notification command for object 'host.name!apt-updates' (PID: 1492056, arguments: '/usr/lib/nagios/plugins/notify_zammad' '--check-output' 'APT CRITICAL: 3 packages available for upgrade (3 critical updates). linux-libc-dev (security)' '--check-state' 'CRITICAL' '--host-name' 'host.name' '--notification-type' 'CUSTOM' '--secure' '--service-name' 'apt-updates' '--token' 'XXX' '--zammad-customer' 'svc_icinga_mail' '--zammad-group' '0 - Dispatching' '--zammad-hostname' 'support.xx.xxx' '--zammad-port' '443') terminated with exit code 3, output: [UNKNOWN] - unable to parse search results: json: cannot unmarshal array into Go value of type zammad.TicketSearchResult (*fmt.wrapError)

How to recreate the bug?

Try to send a notification via the "notify_zammad" plugin

[martialblog]

Since we did not change any logic or semantic in the version, I assume it could maybe be the Zammad API that changed. Did you update by any chance?

I saw some breaking "changes to search API endpoints":

https://github.com/zammad/zammad/blob/develop/BREAKING_CHANGES.md#changes-to-search-api-endpoints

[citfs]

We also updated Zammad to the latest version last week. So that's probably where the problem really comes from.

I assume we are no longer allowed to pass the ‘Ticket Group’ parameter. I will test this and give feedback here.

[citfs]

Unfortunately, simply not passing the ‘zammad-group’ parameter does not work.

I then get the following error message:
[UNKNOWN] - required flag(s) "zammad-group" not set (*errors.errorString)

[tbauriedel]

ref/NC/853875