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

[BUG] Edit issue summary is broken #5601

Closed
3 of 4 tasks
TechCare-Aus opened this issue Aug 7, 2020 · 4 comments
Closed
3 of 4 tasks

[BUG] Edit issue summary is broken #5601

TechCare-Aus opened this issue Aug 7, 2020 · 4 comments
Assignees

Comments

@TechCare-Aus
Copy link
Contributor

Prerequisites

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

For more information on how to write a good bug report

Description

Latest git commits (as of 07/AUG/2020).
Issue changing the name of a support ticket. Everything appears to work like normal, but no change is made.

Steps to Reproduce

  1. Edit any support ticket
  2. Change the issue summary
  3. Save
  4. No change is made

Expected behavior: [What you expected to happen]

Issue summary to change from old to new.

Actual behavior: [What actually happened]

Nothing changes. Although it does get recorded but where it normally says the change = nothing.

image

Versions

osTicket Version | v1.14.2-100-g46d2ea5f (46d2ea5) —  Up to date
Web Server Software | Apache
MySQL Version | 10.3.23
PHP Version | 7.3.20

I was running on PHP v7.4 but changed to v7.3 in case that was the problem. Still an issue.
No errors in PHP log.
No errors in the log inside osTicket.
No errors shown using the development options in Edge.
I've tried using Edge, Edge In Private, Chrome, FireFox Incognito. All experience the same issue.

@TechCare-Aus
Copy link
Contributor Author

I believe something in the latest commit changes has caused this issue. Because it was working a day ago and I just updated to the latest commits this morning.

@TechCare-Aus
Copy link
Contributor Author

@aydreeihn - is there anything I can do to help with this? Super annoying that I cannot change the Issue Summary at the moment. Totally get it that it's my own fault for running git version to by the way so no issue there :)

@aydreeihn
Copy link
Contributor

@TechCare-Aus PR #5610 addresses the issue with being able to save fields at least. I am also working on a fix that will correct the thread events at the bottom of the ticket.

@TechCare-Aus
Copy link
Contributor Author

@aydreeihn - just confirming that the #5610 has fixed the issue experienced. Thank you for that.

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