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>
66 lines
2.2 KiB
ReStructuredText
66 lines
2.2 KiB
ReStructuredText
==========================================
|
|
Create a Schedule and Make Encoding Easier
|
|
==========================================
|
|
|
|
Organize regular schedules or forecast projects in a long term basis. Create shifts to manage your
|
|
tasks, assign employees, and stay organized at a high level.
|
|
|
|
Organize your team by roles
|
|
===========================
|
|
|
|
Go to :menuselection:`Configuration --> Roles --> Create`.
|
|
Optionally, go to the *Employees* application, select the respective employee, and under *Work
|
|
Information* select the *Default Planning Role*.
|
|
|
|
.. image:: duplicate_a_planning/cs1.png
|
|
:align: center
|
|
:alt: Roles in Odoo Planning Application
|
|
|
|
Make shifts recurrent
|
|
=====================
|
|
|
|
While creating a shift, select *Repeat* and configure as needed, saving you from the need
|
|
of re-planning it.
|
|
|
|
.. image:: duplicate_a_planning/cs2.png
|
|
:align: center
|
|
:alt: Repeat shifts in Odoo Planning Application
|
|
|
|
.. note::
|
|
Repeated shifts are generated for the next six months. A modification is possible in
|
|
:ref:`developer mode <developer-mode>`, from *Settings*.
|
|
|
|
.. image:: duplicate_a_planning/rate_shift_generation.png
|
|
:align: center
|
|
:alt: Repeat shifts in Odoo Planning Application
|
|
|
|
.. tip::
|
|
To duplicate a shift in the Gantt view, press CTRL + drag and drop.
|
|
|
|
Save shifts as templates
|
|
========================
|
|
|
|
If creating a shift on the fly and know you might use that template in the future, click on *Save as
|
|
a Template*.
|
|
|
|
.. image:: duplicate_a_planning/cs3.png
|
|
:align: center
|
|
:alt: Save shift as a Template in Odoo Planning Application
|
|
|
|
.. tip::
|
|
To create a template in advance, go to :menuselection:`Configuration --> Shifts Templates -->
|
|
Create`.
|
|
|
|
Duplicate a planning from the previous week
|
|
===========================================
|
|
|
|
When in the Gantt view, either under *Schedule by Employee, Role or Project*, instead of re-planning
|
|
shifts that have been planned before, simply click on *Copy Previous Week*.
|
|
|
|
.. image:: duplicate_a_planning/cs4.png
|
|
:align: center
|
|
:alt: Shift recurrency in Odoo Planning Application
|
|
|
|
.. note::
|
|
The integration with the *Time off* and *Employee* applications, show you grayed cells to the
|
|
days when the employee does not work and is on vacation time, for example. |