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

The previous message remains filled in #6688

Open
SBA-Lars opened this issue Apr 23, 2024 · 1 comment
Open

The previous message remains filled in #6688

SBA-Lars opened this issue Apr 23, 2024 · 1 comment

Comments

@SBA-Lars
Copy link

Prerequisites

  • [YES] Can you reproduce the problem in a fresh installation of the "develop" branch?
  • [NO] Do you have any errors in the PHP error log, or javascript console?
  • [YES] Did you check the osTicket forums?
  • [YES] Did you perform a cursory search to see if your bug or enhancement is already reported?

Description

When an employee has sent a message and then opens the ticket again, the previous response is still there.
Even when they open the ticket in incognito (without cache and cookies) the previous response is still filled in.
This is very similar to what the auto save functionality does. Could it be that the auto save function is causing this issue?

Steps to Reproduce

  1. Send a ticket to a customer
  2. Receive a response
  3. Write a new message and you see that this WYSIWYG editor is already filled with the previous message

Expected behavior: [An empty WYSIWYG editor]

Actual behavior: [An empty WYSIWYG editor, with the previouse send message]

Versions [v1.18]

Admin panel -> Dashboard -> Information which also additionally gives you information about your server.

Also, please include the OS and what version of the OS you're running. As well as your browser and browser version.
image
We are using Google Chrome as browser

@JediKev
Copy link
Contributor

JediKev commented Apr 23, 2024

@SBA-Lars

Any reason you aren't using the latest v1.18.1? Can you try retesting with the latest version? If it's still an issue then maybe it's a bug where we aren't clearing the Draft after creating a Ticket, etc.

Cheers.

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