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

Assistance Needed: Reports Module Issue #4443

Closed
SecteurA opened this issue Dec 30, 2024 · 7 comments
Closed

Assistance Needed: Reports Module Issue #4443

SecteurA opened this issue Dec 30, 2024 · 7 comments

Comments

@SecteurA
Copy link

Hello,

The Reports module has stopped functioning, as shown in the attached screenshot. Additionally, our tickets database has grown to 197 GB.

We would appreciate your assistance in resolving this issue and restoring the module's functionality.

Thank you for your support.
Capture d’écran 2024-12-30 à 10 19 14

@freescout-help
Copy link
Collaborator

Check errors in the browser console and in Manage > Logs > App Logs.

@SecteurA
Copy link
Author

Hello,

Thank you for your response, i can't see any error when i refresh the reports module, the App Logs are still empty.

And for the Console issues it shows 4 issues, but i don't know how to read them
Capture d’écran 2024-12-30 à 12 45 20

Capture d’écran 2024-12-30 à 12 42 33 Thanks

@Celestron2835
Copy link

We are also seeing the same issue in our instance. The year is defaulting to 2025, and the System -> Status page shows the date and time as 2025 even though the Ubuntu 24.04 OS time is correct.

@pcreadycl
Copy link

Hi, same here, no error in logs, no error un console, fresh install. not work.

@freescout-help
Copy link
Collaborator

Fixed in the master branch and will be published in the next release.

Reports will start working on January 1st or meanwhile you can simply change "2025" to "2024" in the report date field:
2024-12-31_09-04-34

@SecteurA
Copy link
Author

Thank you so much for solving it !

@SecteurA
Copy link
Author

SecteurA commented Jan 1, 2025

Yeah it's been solved. Thanks

@SecteurA SecteurA closed this as completed Jan 1, 2025
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

4 participants