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>
45 lines
1.7 KiB
ReStructuredText
45 lines
1.7 KiB
ReStructuredText
===========================================================
|
|
Send Planned Shifts and Give Employees Autonomy Over Shifts
|
|
===========================================================
|
|
|
|
If you are not on top of your tasks and shifts you might fall behind, losing productivity.
|
|
Allowing your employees to have a say over shifts helps you to be on top of your workload, and
|
|
gives them flexibility.
|
|
|
|
Publish and send the planned week by email
|
|
==========================================
|
|
|
|
Once you have your shifts planned, click on *Send Schedule*. Select *Include Open shift* if
|
|
you would like the *Unassigned* shifts to be seen.
|
|
|
|
.. image:: send_planned_shifts/sp1.png
|
|
:align: center
|
|
:alt: Publish and Send planned shifts in Odoo Planning Application
|
|
|
|
Choose if you just want to *Publish* or *Publish and Send*. If you *Publish and Send*, employees
|
|
get an email that redirects them to their planned tasks:
|
|
|
|
.. image:: send_planned_shifts/sp2.png
|
|
:alt: Publish and Send planned shifts in Odoo Planning Application
|
|
|
|
.. note::
|
|
Employees will not be able to see shifts until they have been published.
|
|
|
|
Let employees unassign themselves from shifts
|
|
=============================================
|
|
|
|
Go to *Configuration* and enable *Allow Unassignment*.
|
|
From now on, when an employee opens his tasks, he can indicate his unavailability clicking
|
|
on *I am unavailable*. The shift will be opened again, allowing someone else to take it.
|
|
|
|
.. image:: send_planned_shifts/sp3.png
|
|
:align: center
|
|
:alt: Allow Unassignment in Odoo Planning Application
|
|
|
|
.. image:: send_planned_shifts/sp4.png
|
|
:align: center
|
|
:alt: Allow Unassignment in Odoo Planning Application
|
|
|
|
.. tip::
|
|
Employees have portal access; users have access to the database.
|