[17.0][MIG] project_timeline: Migration to version 17.0 #1354
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
========================== Timeline view for projects ========================== This module extends the standard tasks actions to add the timeline view to them, and also adds the needed fields in the view for handling them. Usage ===== * Go to *Project > Project > Tasks*. * Click on the icon with a clock. * You will see the tasks in the new view.
* [IMP] Add start and end date in task form view * [IMP] Add start and end date in task form view
Currently, if `date_end` is not set it will result in a KeyError.
…_state : blocked tasks are red and task without user are white [IMP] project_timeline : planned_hours is displayed only if not null
Modules that bring `gantt` and `map` view mode are not declared in module dependency Those modes were introduced by https://github.com/OCA/project/pull/869/files#r785447743
Currently translated at 33.3% (2 of 6 strings) Translation: project-15.0/project-15.0-project_timeline Translate-URL: https://translation.odoo-community.org/projects/project-15-0/project-15-0-project_timeline/pt_BR/
Removed oca_dependencies file as longer needed
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: project-16.0/project-16.0-project_timeline Translate-URL: https://translation.odoo-community.org/projects/project-16-0/project-16-0-project_timeline/
Currently translated at 100.0% (3 of 3 strings) Translation: project-16.0/project-16.0-project_timeline Translate-URL: https://translation.odoo-community.org/projects/project-16-0/project-16-0-project_timeline/de/
This prevents "no timeline view found" error. This is based in PR OCA#1152
Currently translated at 100.0% (3 of 3 strings) Translation: project-16.0/project-16.0-project_timeline Translate-URL: https://translation.odoo-community.org/projects/project-16-0/project-16-0-project_timeline/pt_BR/
Currently translated at 100.0% (3 of 3 strings) Translation: project-16.0/project-16.0-project_timeline Translate-URL: https://translation.odoo-community.org/projects/project-16-0/project-16-0-project_timeline/es/
Currently translated at 100.0% (3 of 3 strings) Translation: project-16.0/project-16.0-project_timeline Translate-URL: https://translation.odoo-community.org/projects/project-16-0/project-16-0-project_timeline/nl/
This commit fixes inconsistent dates we get when building a demo DB. This module adds a `date_start` field; this is the one we want to fill in demo data. We do not want to fill `date_assign`, which is an automatic field. This is how this module used to work in v12 (was based on `date_start`). * v12➔v13 MIG: Odoo removed the base `date_start` field so `date_start` was changed to `date_assign` in this module. * v13➔v14 MIG: `date_start` was added back into this module to restore v12 behavior. However, demo data then got left untouched.
Ensure `date_start` (added by this module) is always before `date_end` (base Odoo field in the `project` module).
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: project-16.0/project-16.0-project_timeline Translate-URL: https://translation.odoo-community.org/projects/project-16-0/project-16-0-project_timeline/
Currently translated at 100.0% (4 of 4 strings) Translation: project-16.0/project-16.0-project_timeline Translate-URL: https://translation.odoo-community.org/projects/project-16-0/project-16-0-project_timeline/it/
Currently translated at 100.0% (4 of 4 strings) Translation: project-16.0/project-16.0-project_timeline Translate-URL: https://translation.odoo-community.org/projects/project-16-0/project-16-0-project_timeline/es_AR/
Currently translated at 100.0% (4 of 4 strings) Translation: project-16.0/project-16.0-project_timeline Translate-URL: https://translation.odoo-community.org/projects/project-16-0/project-16-0-project_timeline/pt_BR/
The fields `date_assign` and `date_end` can't be used, as they are automatically rewritten on certain flow events (user assignation and stage changed to finished one), so we need dedicated fields for the planning. A previous change switches `date_assign` to `date_start`, but it didn't change demo data, and better to use a consistent naming, prefixing both fields with `planned_`. This includes the migration scripts for preserving previous data, and automations to fill planned data from the previous fields. It also pre-fills planning information from assignation date/close date as a best effort pre-planning for existing tasks. TT50618 Co-Authored-By: Pedro M. Baeza <[email protected]> [IMP] project_timeline: Add planned_date_* fields to the task tree view TT50618
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: project-16.0/project-16.0-project_timeline Translate-URL: https://translation.odoo-community.org/projects/project-16-0/project-16-0-project_timeline/
Currently translated at 85.7% (6 of 7 strings) Translation: project-16.0/project-16.0-project_timeline Translate-URL: https://translation.odoo-community.org/projects/project-16-0/project-16-0-project_timeline/es/
Currently translated at 100.0% (7 of 7 strings) Translation: project-16.0/project-16.0-project_timeline Translate-URL: https://translation.odoo-community.org/projects/project-16-0/project-16-0-project_timeline/it/
Currently translated at 100.0% (7 of 7 strings) Translation: project-16.0/project-16.0-project_timeline Translate-URL: https://translation.odoo-community.org/projects/project-16-0/project-16-0-project_timeline/es_AR/
pedrobaeza
approved these changes
Oct 21, 2024
carlos-lopez-tecnativa
force-pushed
the
17.0-mig-project_timeline
branch
from
cd89d7b
to
9946227
Compare
CarlosRoca13
approved these changes
Oct 22, 2024
|
/ocabot merge nobump |
|
On my way to merge this fine PR! |
|
Congratulations, your PR was merged at 3e3e76a. Thanks a lot for contributing to OCA. ❤️ |
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.
Depends on:
TT50999
@Tecnativa @pedrobaeza @victoralmau @chienandalu could you please review this