Znuny and ((OTRS)) Community Edition

I dont even know what this means:

First of all please do not crosspost to different language forums and don't hijack other topics.

if you are going to complain about a post - please be specific and clear so someone can at least understand what the rules are so they may be followed.

There was no mention by anyone - other than OTRS aligned people - in this thread about FREE. It was not part of the original post or other replies. The comments were in regards to the community editions and contributing... the time-honored process and real strength of 'open source' software. Which O...

We are now testing, customizing, pentesting DUO integration with our OTRS 6.0 installations using some of our code and some elements found here. We will be happy to post back the results. However final tests and customization will be on OTOBO and and not OTRS. Like many helping in the OTRS community...

OTRS Gmbh has basically killed any open source version of OTRS after Community Version 6. They will not allow outside contributors and will not releasing any open source versions... possibly against the GPL license they 'should' be tied to. The OTOBO helpdesk project looks like it is taking off from...

If you continually receive the OTRS Scheduler warning in the GUI... "Scheduler process is registered but might no be running." We have found this often occurs after we migrate OTRS server or change the OTRS server hostname and/or IP address. The cause seems to be multiple scheduler process...

Has anyone found a solution to this scheduler issue? We have 4 OTRS 3.1.10 machines (also moved to Linux from a previous Windows install) that are experiencing the same problem.

In case this might help others, we have found the most common reason we get the following OTRS error: Can't create PID PostMasterMailbox, because it's already running is because multiple CRONTAB jobs are created, usually because of tmp files in otrs/var/cron folder. Here is how to check and fix this...

We have found the most common reason we get this error in OTRS setups is that multiple CRONTAB jobs are created. Assuming you are using LINUX, first run the shell command: for user in $(cut -f1 -d: /etc/passwd); do crontab -u $user -l; done This will show you if there are multiple users with OTRS re...

Currently this is not possible without redoing significant code in the notification system.
We are also having a terrible time trying to fix up the agent notification formatting (particularily the line breaks! arghhh) - and we have been working on it for two years.