[19.0][MIG] web_timeline: Migration to 19.0#3521
Merged
Merged
Conversation
* Avoid to display all items of group_by model * Remove unnecessary readgroup * Remove dependency on project. Modify module structure. Imporve readme file. * Add setup.py
* [FIX] Correct write when grouped by * Remove blank lines * Minor changes
* Update the vis.js framework to latest stable version (v4.20.1) to add new functionality and save almost 400ko of source code in odoo assets (the vis dev team has isolate the code for timeline widget from the rest of their widgets) * Add the possibility to display events with no duration (instantaneous) as the same time has regular events * Add the possibility to choose between two scroll mode : - zoom in time resolution (default) or - vertical scroll (web browser default behaviour) Signed-off-by: adrien.didenot <adrien.didenot@horanet.com>
…same as base Calendar view) In Odoo calendar view, the attribute date_delay is an alternative to date_stop, to provides the duration of the event instead of its end date. This commit integrate this attribute to the Timeline view, but contrary to the base Calendar view the Timeline view could use both arguments (date_stop and date_delay) simultaneously. Signed-off-by: adrien.didenot <adrien.didenot@horanet.com>
The default window display all the events (aka 'fit'), in case of events spread over the year, the events are invisibles (too small to be readable) Signed-off-by: adrien.didenot <adrien.didenot@horanet.com>
Change the attribute 'default_window' to 'mode' like the Odoo calendar view (to be iso functional)
CSS classes have changed with the updated version of vis.js
* Update Version in Manifest * Remove enconding in .py files * Rewrite the view definition according to version 11
[IMP] web_timeline: Templates implementation like kanban [ADD] Check if template exists Update README.rst
[UPD] Version number [UPD] README
Update README.rst [FIX] Remove console.log [ADD] Make timeline.fit optional [FIX] Use stringified points [IMP] Reversed the arrow head and fixed lint issues [IMP] Use options parameter for line color and width [FIX] Version number [IMP] Minor improvements
[IMP] Prevent flickering [IMP] Fixed headers [ADD] Create new record by date range selection Remove roadmap item from readme [FIX] minimal height
[FIX] web_timeline: Reloading view [FIX] web_timeline: Reloading view
When trying to order by a field of type many2many, Odoo up to version 17 does not raise an error, it only displays a warning in the log (e.g. in the module sale_timesheet_timeline when grouping by task_user_ids): WARNING sale_timesheet_timeline odoo.models: Model 'sale.order.line' cannot be sorted on field 'task_user_ids' (not a column). But starting from Odoo 18, this warning is now raised as an exception, so it becomes impossible to group by an m2m field because this module tries to order by the same field as default_group_by. This commit at least prevents the error by avoiding sending the order field to the server in this case, and instead lets the order be taken from the model’s _order attribute.
…perly This issue was introduced during the migration to v18 when converting old jQuery code to native JavaScript in this commit: OCA@258a5a9 Fixes OCA#3420
Append our view_mode this way to avoid overwriting changes done by other modules.
Currently translated at 100.0% (16 of 16 strings) Translation: web-18.0/web-18.0-web_timeline Translate-URL: https://translation.odoo-community.org/projects/web-18-0/web-18-0-web_timeline/es/
Author
|
No new logic was introduced during this migration. Should anything be added to fix the codecov fail? |
This was referenced Apr 23, 2026
|
ping @OCA/web-maintainers |
pedrobaeza
approved these changes
Apr 30, 2026
Member
pedrobaeza
left a comment
pedrobaeza
left a comment
There was a problem hiding this comment.
/ocabot migration web_timeline
/ocabot merge nobump
Contributor
|
Hey, thanks for contributing! Proceeding to merge this for you. |
Contributor
|
Congratulations, your PR was merged at 201cb86. Thanks a lot for contributing to OCA. ❤️ |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
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.
The previous migration attempt (#3401 by @bizzappdev) appears to have been abandoned. This PR picks up that work and completes the migration.