-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Schedule: adding a repeated event #17385
Comments
I just tested with the new version 10.0.16 and the bug is still present. |
Nobody has the bug? |
Hi, I confirm the issue. A repeated event is not displayed in the "All day" row (at top of the planning) as it should. |
Hello, do you have any updates regarding this bug? Thx. |
Hello, Bug still there in version 10.0.17. |
I just took a look, I can reproduce, but I've not been able to find what the issue is. |
I just tested several earlier versions of GLPI, and it turns out that this bug has been present since the first release of GLPI 10 (10.0.0-RC1). |
@cconard96 Thank you very much, the change does fix the issue! However, I noticed an unexpected behavior with the calendar in Thunderbird, while there are no issues with Google Calendar. Thunderbird : Google Calendar : |
Code of Conduct
Is there an existing issue for this?
Version
10.0.16
Bug description
When we add an external event lasting "1 day" repeated (for example every week with an interval of 3). Then, the event in the schedule view is not displayed in the "All day" box but as an event with a duration from 0:00 to 23:00.
If we remove the repetition, then the event is placed in the correct box, i.e. "All day".
Relevant log output
No response
Page URL
No response
Steps To reproduce
1 - Add an external event, with a duration of "1 day", then have it repeat every week with an interval of 3.
Your GLPI setup information
Informations sur le système, l'installation et la configuration
Server
GLPI constants
Libraries
SQL replicas
Notifications
Plugins list
Anything else?
No response
The text was updated successfully, but these errors were encountered: