Browseable collection of plugins for the popular ticket system software Znuny and ((OTRS)) Community Edition.
Version 5.0.1 by Ciphron on 04 Nov 2015 // Framework: 5.0.x
Holidays 2015 - 2030 Saarland.
Version 5.0.1 by Ciphron on 04 Nov 2015 // Framework: 5.0.x
Holidays 2015 - 2030 Saxony.
Version 5.0.1 by Ciphron on 04 Nov 2015 // Framework: 5.0.x
Holidays 2015 - 2030 Thuringia.
Version 4.0.1 by Ciphron on 03 Nov 2015 // Framework: 4.0.x
No state change on Vacation Message for OTRS 4.0.x.
Version 4.0.1 by Ciphron on 03 Nov 2015 // Framework: 4.0.x
Remove the OTRS GROUP Package no Verification Warning for OTRS 4.0.x.
Version 4.0.1 by Ciphron on 03 Nov 2015 // Framework: 4.0.x
Convert the ".MSG" to ".EML" Attachment-Files in E-Mails for OTRS 4.0.x.
Version 0.9.9 by Artjoms on 12 Aug 2015 // Framework: 3.x.x
Dashboard widget with sound Alert
Version 1.0.0 by seberget on 24 May 2015 // Framework: 3.3.x
This module will go through all tickets that have been created by the System monitoring plug-in last week and create a new Problem ticket if there where more than 3 recurring issues found (configurable). The selection is done on the basis of 'CustomerId', 'Host' and 'Service. This module is run like a 'cron' job from GenericAgent. All the data is found by custom SQL code, so you need to 'fake' a ticket. Just find your oldest ticket number, and add it to the top. You select which days to run. I've set it up to run on Mondays, therefore you need to set the fromDays to be 8, and the toDays to be 1. There are also templating for the text. See the SystemMonitoringReporting category in SysConfig for more information. Check also out the two images 'png' files added to the docs directory for help on the configuration.
Version 1.0.0 by seberget on 24 May 2015 // Framework: 3.3.x
This module fixes the pending time if the ticket is answered on a non working day, or the pending date itself is placed on an non working day. If the new calculated Pending date is outside the lifetime of the session, this functionality is bypassed, as it is assumed that the pending date have been changed on purpose. Basically it will only take effect if the automatic pending date comes on a non working day/hour. It calculates the difference in days, and working hours. And uses the 'DestinationTime' method from the 'Kernel::System::Ticket' module to place it on a correct day. It uses 'Monday' as the day to calculate the working hours, from the tickets queue calendar.