==========================
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

* Timeline for project.project (OCA#398)

  Creates a timeline for projects. Useful for huge campaigns with multiple projects.

* Unsetting date_end (OCA#402)

* Tests

* Task timeline template (OCA#410)

Currently, if `date_end` is not set it will result in a KeyError.

…e (major change)

…_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/

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/es_AR/

In Odoo 16, project forms already have these 2 date fields with a nice
date-range widget.

The view being removed here adds these date fields at the top of the
form (next to an invisible field).

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/fr/

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/sv/

Unassigned tasks are supposed to show up in white instead of default
color, but the previous `== []` comparison is no longer working in Odoo
16 / with web_timeline 16.0.1.0.3.

This is because web_timeline forces string conversion during evaluation
of these color instructions, and an empty `user_ids` is an empty string
in this case.

This does look somewhat odd but fixes the issue short of rewriting
py-eval instructions in web_timeline, which would be a much larger task.

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/