We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Impacted versions: 14.0 Enterprise
Steps to reproduce: When using the calendar popup create method, the create form is not working as expected.
In the first video (1-calendar-create.gif) we see the expected behavior.
In the second video (2-calendar-drag-nochange.gif):
In the thired video (3-calendar-drag-create.gif):
The issue can be reproduced on a fresh database with the "Time Off" application installed.
Current behavior: Duration is not calculated correctly and the start/end date is not correct when not changed in popup edit form
Expected behavior: Duration, start- and enddate should be correct in popup create form.
Support ticket number submitted via odoo.com/help (optional): #2448112
The text was updated successfully, but these errors were encountered:
The Odoo support showed me a work around for this issue by reselecting the time off type.
Sorry, something went wrong.
No branches or pull requests
Impacted versions: 14.0 Enterprise
Steps to reproduce:
When using the calendar popup create method, the create form is not working as expected.
In the first video (1-calendar-create.gif) we see the expected behavior.
In the second video (2-calendar-drag-nochange.gif):
In the thired video (3-calendar-drag-create.gif):
The issue can be reproduced on a fresh database with the "Time Off" application installed.
Current behavior:
Duration is not calculated correctly and the start/end date is not correct when not changed in popup edit form
Expected behavior:
Duration, start- and enddate should be correct in popup create form.
Support ticket number submitted via odoo.com/help (optional):
#2448112
The text was updated successfully, but these errors were encountered: