documentation/content/applications/services/project/planning/forecast.rst
Antoine Vandevenne (anv) 6f125de01b [MOV] content/*: move resource files into their related page's directory
Since odoo/documentation#903, the guideline for the location of new
resource (images, downloadable files, RST includes...) files is to place
those inside the directory of the RST page that references them.

For example, if `doc1.rst` has a reference to `image.png` and to
`download.zip`, the file structure should look like this:

├── parent_doc/
│     └── doc1/
│     │     └── image.png
│     │     └── download.zip
│     └── doc1.rst
│     └── doc2.rst
├── parent_doc.rst

Before this commit, most of the resource files were still located inside
'media' directories holding all the resource files referenced by RST
pages located at the same level as these directories. In the example
above, a single 'media' directory would hold all the resource files
referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from
figuring out easily which resource file was referenced by which RST page
and, thus, lead to unused resource files piling up in the repository. It
also made it more complicated to define codeowners regex rules because a
team could not simply be assigned to `/some_page.*` but needed to be
assigned to both `/some_page\.rst` and to the location of 'media'.

In order to help new content writers figure out the guideline when
taking examples from other RST pages, this commit retroactively applies
the guideline to existing resource files and 'media' directories. The
left-over resource files that are not referenced by any RST page are
removed.

task-2497965

closes odoo/documentation#2006

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
2022-05-19 11:33:49 +02:00

48 lines
2.0 KiB
ReStructuredText
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

==================================
Forecast Resources Across Projects
==================================
Allocate the needed time for specific tasks under a planned shift. Once that is done, analyse Key
Performance Indicators (KPIs), so you can evaluate your employees performance and workload, besides
the progress of your projects/tasks when comparing the planned and effective hours.
Allocate times under shifts
===========================
When planning a shift, in the *Planning* application, create a project and a task on the fly,
or simply select the one you want.
.. image:: forecast/allocate_time.png
:align: center
:alt: Planning form to choose the project, task and allocated hours in Odoo Planning
| *Allocated Time (%)* allows you to define the percentage of time you would like your employee to
work on that specific task during his shift. See that information in hours on *Allocated hours*.
| The calculation shows you how many hours out of the total shift time (*End date* - *Start date*)
are spent by the employee on that task.
| On :menuselection:`Project --> Planning --> By Project`, immediately see the total number of
employees allocated per project.
.. image:: forecast/planning_project.png
:align: center
:alt: Planning by project view in Odoo Project
Compare forecast hours with the effective ones
==============================================
Now, once the employee has timesheeted his hours in the task, go to *Project* and with the
*View list*, under *All Tasks*, conveniently see the *Planned Hours* compared to the
*Remaining Hours*, and a calculation of the *Progress*.
.. image:: forecast/compare_forecast.png
:align: center
:alt: View of all tasks and their planned and remaining hours in Odoo Project
.. important::
Reminder: the option *Timesheets* has to be enabled on your project.
.. image:: forecast/enable_timesheets.png
:align: center
:height: 400
:alt: Under the settings of a project enable timesheets in Odoo Project