-
Notifications
You must be signed in to change notification settings - Fork 8.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
[FW][IMP] marketing: match the Display Timezone description with tooltips #11815
Open
fw-bot
wants to merge
1
commit into
saas-18.1
Choose a base branch
from
saas-18.1-16.0-opw-4323142-display_timezone_event_form-lase-Jofl-fw
base: saas-18.1
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[FW][IMP] marketing: match the Display Timezone description with tooltips #11815
fw-bot
wants to merge
1
commit into
saas-18.1
from
saas-18.1-16.0-opw-4323142-display_timezone_event_form-lase-Jofl-fw
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Issue: The current descriptions and naming of the `Date` fields (`date_begin`, `date_end`) and the `Timezone` field (`date_tz`) can be confusing in the form view of the event model. Specifically: The timezone used for converting the form dates to the database is determined by the context and not by the `Timezone` field present on the form. However, this `Timezone` field determines the timezone used for displaying the event's date/time on the website. This change clarifies the situation according to the update done in the community PR opw-4323142 X-original-commit: fe9d186
This PR targets saas-18.1 and is part of the forward-port chain. Further PRs will be created up to master. More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port |
robodoo
pushed a commit
to odoo/odoo
that referenced
this pull request
Jan 22, 2025
Issue: The current descriptions and naming of the `Date` fields (`date_begin`, `date_end`) and the `Timezone` field (`date_tz`) can be confusing in the form view of the event model. Specifically: The timezone used for converting the form dates to the database is determined by the context and not by the `Timezone` field present on the form. However, this `Timezone` field determines the timezone used for displaying the event's date/time on the website. This change tries to clarify the situation. opw-4323142 closes #194671 X-original-commit: 88813db Related: odoo/documentation#11815 Signed-off-by: Lancelot Semal (lase) <[email protected]> Signed-off-by: Jérémy Hennecart (jeh) <[email protected]>
robodoo
pushed a commit
that referenced
this pull request
Jan 22, 2025
Issue: The current descriptions and naming of the `Date` fields (`date_begin`, `date_end`) and the `Timezone` field (`date_tz`) can be confusing in the form view of the event model. Specifically: The timezone used for converting the form dates to the database is determined by the context and not by the `Timezone` field present on the form. However, this `Timezone` field determines the timezone used for displaying the event's date/time on the website. This change clarifies the situation according to the update done in the community PR opw-4323142 closes #11815 X-original-commit: fe9d186 Related: odoo/odoo#194671 Signed-off-by: Lancelot Semal (lase) <[email protected]>
robodoo
pushed a commit
to odoo/odoo
that referenced
this pull request
Jan 22, 2025
Issue: The current descriptions and naming of the `Date` fields (`date_begin`, `date_end`) and the `Timezone` field (`date_tz`) can be confusing in the form view of the event model. Specifically: The timezone used for converting the form dates to the database is determined by the context and not by the `Timezone` field present on the form. However, this `Timezone` field determines the timezone used for displaying the event's date/time on the website. This change tries to clarify the situation. opw-4323142 closes #194671 X-original-commit: 88813db Related: odoo/documentation#11815 Signed-off-by: Lancelot Semal (lase) <[email protected]> Signed-off-by: Jérémy Hennecart (jeh) <[email protected]>
robodoo
pushed a commit
that referenced
this pull request
Jan 22, 2025
Issue: The current descriptions and naming of the `Date` fields (`date_begin`, `date_end`) and the `Timezone` field (`date_tz`) can be confusing in the form view of the event model. Specifically: The timezone used for converting the form dates to the database is determined by the context and not by the `Timezone` field present on the form. However, this `Timezone` field determines the timezone used for displaying the event's date/time on the website. This change clarifies the situation according to the update done in the community PR opw-4323142 closes #11815 X-original-commit: fe9d186 Related: odoo/odoo#194671 Signed-off-by: Lancelot Semal (lase) <[email protected]>
robodoo
pushed a commit
to odoo/odoo
that referenced
this pull request
Jan 22, 2025
Issue: The current descriptions and naming of the `Date` fields (`date_begin`, `date_end`) and the `Timezone` field (`date_tz`) can be confusing in the form view of the event model. Specifically: The timezone used for converting the form dates to the database is determined by the context and not by the `Timezone` field present on the form. However, this `Timezone` field determines the timezone used for displaying the event's date/time on the website. This change tries to clarify the situation. opw-4323142 closes #194671 X-original-commit: 88813db Related: odoo/documentation#11815 Signed-off-by: Lancelot Semal (lase) <[email protected]> Signed-off-by: Jérémy Hennecart (jeh) <[email protected]>
robodoo
pushed a commit
that referenced
this pull request
Jan 22, 2025
Issue: The current descriptions and naming of the `Date` fields (`date_begin`, `date_end`) and the `Timezone` field (`date_tz`) can be confusing in the form view of the event model. Specifically: The timezone used for converting the form dates to the database is determined by the context and not by the `Timezone` field present on the form. However, this `Timezone` field determines the timezone used for displaying the event's date/time on the website. This change clarifies the situation according to the update done in the community PR opw-4323142 closes #11815 X-original-commit: fe9d186 Related: odoo/odoo#194671 Signed-off-by: Lancelot Semal (lase) <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue:
The current descriptions and naming of the
Date
fields (date_begin
,date_end
) and theTimezone
field (date_tz
) can be confusing in the form view of the event model. Specifically:The timezone used for converting the form dates to the database is determined by the context and not by the
Timezone
field present on the form. However, thisTimezone
field determines the timezone used for displaying the event's date/time on the website. This change clarifies the situation according to the update done in the community PRopw-4323142
Forward-Port-Of: #11749
Forward-Port-Of: #11596