Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replies merging with incorrect threads #4258

Closed
hendrikIK opened this issue Sep 30, 2024 · 6 comments
Closed

Replies merging with incorrect threads #4258

hendrikIK opened this issue Sep 30, 2024 · 6 comments

Comments

@hendrikIK
Copy link

My client is using the FreeScout ticketing system.

They reported an issue where their users would reply to a thread and have their message attached to a different, unrelated thread. At the time, they were running version 1.8.104 of FreeScout, so I upgraded them to version 1.8.153.

They reported that the issue persists; a user replied to their own thread, and the message got attached to a different email thread with a different ticket number. The only consistency I could pick up on was that it tends to attach to closed tickets.

My client's FreeScout system is running inside a Linux Ubuntu VM within a Docker container.

The modules that my client set up are the following:
API and Webhooks: 1.0.71
Custom Folders: 1.0.18
Export Conversations: 1.0.8
Reports: 1.0.35
Tags: 1.0.36
Ticket Number: 1.0.2

PHP version: 8.2.22
FreeScout version: 1.8.153
Database: MySQL
Are you using CloudFlare: No
Are you using non-official modules: No

@freescout-help
Copy link
Collaborator

Most likely their client is also using FreeScout, and that FreeScout is of an version and has to be upgraded.

@hendrikIK
Copy link
Author

Unfortunately, I cannot disclose how my client operates.

Their clients send emails to the ticketing system via Gmail or outlook, they don't use Freescout themselves.

@freescout-help
Copy link
Collaborator

There was an issue in the past when incoming replies from customers were joining to the incorrect conversation but it was happening when the customer was also using the FreeScout. So it looks like we can't help here, you'll need to debug it by yourself on your server: https://github.com/freescout-help-desk/freescout/wiki/Debugging

@hendrikIK
Copy link
Author

Regarding debugging, could you give me some guidance on where to investigate the issue in the database?

Details such as how conversations, threads, and tickets link to each other and how the data is structured in the context mentioned above.

Would it also be possible to give me the version number where the above-mentioned issue was fixed?

Your guidance would greatly be appreciated.

@freescout-help
Copy link
Collaborator

Would it also be possible to give me the version number where the above-mentioned issue was fixed?

#2375 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants