6f125de01b
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>
43 lines
1.7 KiB
ReStructuredText
43 lines
1.7 KiB
ReStructuredText
=============================================
|
||
Manage your Employees’ Schedules and Time Off
|
||
=============================================
|
||
The integration with the *Time off* application allows you to quickly see your employees’
|
||
availabilities. It will avoid conflicts and errors between employees schedules and interventions.
|
||
|
||
Effortlessly see employees’ time off
|
||
====================================
|
||
No configuration needs to be done.
|
||
Once the employees’ time has been validated in the *Time off* application, cells will be grayed for
|
||
those days in your Gantt view.
|
||
|
||
It also adapts to the working calendar of the employee. Example: the employee works part-time
|
||
(from Monday to Wednesday). So, Thursday and Friday will also be greyed, in addition to the weekends.
|
||
|
||
.. image:: manage_employees_schedule/mw1.png
|
||
:alt: Employees' Time off in Odoo Field Service
|
||
|
||
Easily manage employees’ schedules
|
||
==================================
|
||
From the Gantt view (under *Planning by User, Project or Worksheet*), click on the plus sign to add
|
||
a new task or on the magnifying glass to plan an existing one.
|
||
|
||
.. image:: manage_employees_schedule/mw2.png
|
||
:align: center
|
||
:alt: Manage employees' schedules in Odoo Field Service
|
||
|
||
Unassigned tasks
|
||
=================
|
||
If you need to plan an intervention but you do not know yet who will take care of it, you can leave
|
||
the task unassigned. It will still be shown in the Gantt view. Simply drag and drop the responsible
|
||
person he can be assigned.
|
||
|
||
.. image:: manage_employees_schedule/mw3.png
|
||
:align: center
|
||
:alt: Unassigned tasks in Odoo Field Service
|
||
|
||
.. tip::
|
||
Create projects per team, or per working site, and have a more accurate and dynamic database.
|
||
|
||
.. seealso::
|
||
* :doc:`/applications/services/project/overview/setup`
|