Znuny mixing up tickets

[tessiof]

Hi,

Znuny works great 99% of the time, but eventually it mixes up some tickets.
For example, imagine an user responding to Ticket#0000000009 but his response ends up on Ticket#Ticket#0000000004. I'm attaching a screenshot that shows this happening to me.

Here are some commands I tried without success before creating this topic:

(1) Check database as root
mariadb-check --all-databases

(2) Check configuration
bin/otrs.Console.pl Admin::Config::ListInvalid
bin/otrs.Console.pl Maint::Config::Rebuild --cleanup

(3) Clear cache
bin/otrs.Console.pl Maint::Cache::Delete
otrs/bin/otrs.Console.pl Maint::Loader::CacheCleanup
bin/otrs.Daemon.pl stop
cd var/tmp/
mv CacheFileStorable/ ~/CacheFileStorable.bak
bin/otrs.Daemon.pl start

[root]

Hello,

Please check the communication log for the wrong follow-ups. You will find probably the reason there why are mixed.

- Roy

[hkais]

Hi,

Znuny works great 99% of the time, but eventually it mixes up some tickets.
For example, imagine an user responding to Ticket#0000000009 but his response ends up on Ticket#Ticket#0000000004. I'm attaching a screenshot that shows this happening to me.

If your other party is using also OTRS or Znuny it is a high probability of a clash of the Ticket Numbers.
This is a known issue in OTRS and Znuny for already a long time.

If the other Party is not using Znuny or OTRS there is a probability that the end users are simply going to inbox and picking any "last" e-mail to reply.
Lazy users, without knowledge what happens with ticket systems...

Cannot imagine anything other

[hkais]

Znuny works great 99% of the time, but eventually it mixes up some tickets.
For example, imagine an user responding to Ticket#0000000009 but his response ends up on Ticket#Ticket#0000000004. I'm attaching a screenshot that shows this happening to me.

Could you give us a update on your topic?