Znuny and ((OTRS)) Community Edition

Could this be my issue ?
Is it safe to remove that line ?

I had to install both Moo & namespace::clean indeed. Here is the error from the apache log; ERROR: OTRS-CGI-10 Perl: 5.16.3 OS: linux Time: Tue Dec 29 16:55:39 2020 Message: Need module! RemoteAddress: 172.xx.x.xxx (I masked) RequestURI: /otrs/index.pl Traceback (1853): Module: Kernel::System::M...

Ok so I just upgraded from 6.0.16 to 6.0.30 today. After some hickups with extra perl modules needed due to Znuny4OTRS the upgrade completed without errors. However after checking the log I get this message for each inbound mail; Dec 29 16:55:19 vslc7otrs01 OTRS-CGI-10[1853]: [Error][Kernel::System:...

I can confirm the update to 6.0.4 fixes the issue.

Thanks, I see in the release notes of 6.0.4 this is indeed fixed.
Will update soon.

Does anyone know the solution ?

I would expect it to be this setting here but the sort is already set at Down instead of Up;

Attachments are now at the bottom of the ticket instead of at the top.
Did you check the bottom of the ticket ?
Which browser do you use ?

Hi Marcel,

Good question I also have this behavior.
After a refresh the newest is back on top but this is kind of annoying indeed.
I haven't found the solution yet.

Awesome !
That works, Thanks a lot for your quick reply !

Hi Roy, Yes I'm aware but ticketnew doesn't have a sort property? Where should I configure it ? https://i.imgur.com/0TrnP4r.png https://i.imgur.com/2G5wvgT.png I tried to add a Sort field and fill in the properties and deployed without error; But still no change; https://i.imgur.com/YSzrKSt.png

Well default it now shows like this; https://i.imgur.com/opblUiw.png When I press at Age at the top of the column it shows in reverse order like https://i.imgur.com/QwLbk0s.png This is what I want it do by default. When I refresh the oldest ticket is back at the top. Which Sysconfig setting is wrong...

Hi, Since the new release 6 my dashboard is sorted with oldest tickets on top. I searched the admin settings to change this and ended up here; https://i.imgur.com/aMbqlpG.png But changing the SortBy field with either "Down" or "Up" doesn"t seem to change the order. Am I miss...

I upgraded the 5.0.23 instance running on CentOS 7 to 6.0.3 yesterday evening. After a few attempts I was able to do so without issues. I did an additional step not documented in the current upgrade guide, but found it in the guide for going from 4 to 5. command bin/otrs.Console.pl Maint::Database::...

Do you have Znuny addons in your local repository ?
I encountered the same issue, removed all local Znuny addons before performing the upgrade and no issue now.

Do you have Znuny addons in your local repository ?
I encountered the same issue, removed all local Znuny addons before performing the upgrade and no issue now.

Ok thx for the help jojo and coolmf ! It seems dropping the database otrs was still required. Here are the steps I've done; On the new instance change password in database mysql for user otrs in table user. drop database otrs; create database otrs CHARACTER SET utf8 COLLATE utf8_general_ci; Perform ...

I've put the password from the old CentOS 6 instance through on online hasher and configured it on the new CentOS 7 mysql. So at this point for user otrs the hashes match on both systems. Tried to run the restore again but still the same issue. ./restore.pl -b /backup/2017-12-14_08-23/ -d /opt/otrs ...

tried to change the password in the old running instance with below commands; mysql> UPDATE mysql.user SET Password=PASSWORD('new password') WHERE User='otrs'; mysql> FLUSH PRIVILEGES; mysql> quit; But afterwards I'm not able to access the interface because of the changes I did to user otrs. So I re...

Yes the password in the current OTRS production instance is different. Unfortunately I don't know the password as it was not setup by me. From a select statement on the old instance it looks like the otrs password is stored hashed. While in the new instance the password is not hashed and shows in pl...

The restore and backup documentation is not complete as I end up with this error; Restore /backup/2017-12-14_08-23//Config.tar.gz ... ERROR: Already existing tables in this database. A empty database is required for restore! So I go to the new empty OTRS 5.0.23 install I created on a CentOS 7.4. And...

OK I confirm the current version running is Perl 5.10.1.

Is there an official migration guide available to move from one host to another ?

Hi,

I'm unable to find details whether or not OTRS 6 Free is supported on CentOS 6 ?
I currently run 5.0.23 on CentOS 6.9.

I'm looking to upgrade to 6 but the RPM is only available for CentOS7 ?

It seems the tickets get locked again to the owner once reply is received on the closed ticket.
So it's not an issue.

Hi, Since I upgraded our OTRS install from 5.0.13 to 5.0.23 all tickets we close are automatically unlocked afterwards. This is not the desired scenario we need as in the case that the customers sends a reply afterwards the users overview doesn't show this new reply. It's only visible by browsing th...