[ADD] planning: add documentation
BIN
_static/banners/planning.jpg
Normal file
After Width: | Height: | Size: 119 KiB |
@ -26,3 +26,4 @@ Applications
|
|||||||
social_marketing
|
social_marketing
|
||||||
sms_marketing
|
sms_marketing
|
||||||
fsm
|
fsm
|
||||||
|
planning
|
||||||
|
11
planning.rst
Normal file
@ -0,0 +1,11 @@
|
|||||||
|
:banner: banners/planning.jpg
|
||||||
|
|
||||||
|
=========
|
||||||
|
Planning
|
||||||
|
=========
|
||||||
|
|
||||||
|
.. toctree::
|
||||||
|
:titlesonly:
|
||||||
|
|
||||||
|
planning/duplicate_a_planning
|
||||||
|
planning/send_planned_shifts
|
62
planning/duplicate_a_planning.rst
Normal file
@ -0,0 +1,62 @@
|
|||||||
|
============================================
|
||||||
|
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:: media/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:: media/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 developer
|
||||||
|
mode, from *Settings*.
|
||||||
|
|
||||||
|
.. 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 knowing that you will use that template in the future,
|
||||||
|
click on *Save as a Template*.
|
||||||
|
|
||||||
|
.. image:: media/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:: media/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.
|
BIN
planning/media/cs1.png
Normal file
After Width: | Height: | Size: 11 KiB |
BIN
planning/media/cs2.png
Normal file
After Width: | Height: | Size: 25 KiB |
BIN
planning/media/cs3.png
Normal file
After Width: | Height: | Size: 18 KiB |
BIN
planning/media/cs4.png
Normal file
After Width: | Height: | Size: 22 KiB |
BIN
planning/media/sp1.png
Normal file
After Width: | Height: | Size: 14 KiB |
BIN
planning/media/sp2.png
Normal file
After Width: | Height: | Size: 12 KiB |
BIN
planning/media/sp3.png
Normal file
After Width: | Height: | Size: 24 KiB |
BIN
planning/media/sp4.png
Normal file
After Width: | Height: | Size: 34 KiB |
45
planning/send_planned_shifts.rst
Normal file
@ -0,0 +1,45 @@
|
|||||||
|
============================================================
|
||||||
|
Send planned shifts and give employees autonomy over shifts
|
||||||
|
============================================================
|
||||||
|
If you are not on top of your tasks and shifts you might fall behind, loosing 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:: media/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
|
||||||
|
will get an email that will redirect them to their planned tasks:
|
||||||
|
|
||||||
|
.. image:: media/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:: media/sp3.png
|
||||||
|
:align: center
|
||||||
|
:alt: Allow Unassignment in Odoo Planning Application
|
||||||
|
|
||||||
|
|
||||||
|
.. image:: media/sp4.png
|
||||||
|
:align: center
|
||||||
|
:alt: Allow Unassignment in Odoo Planning Application
|
||||||
|
|
||||||
|
|
||||||
|
.. tip::
|
||||||
|
Employees have portal access; users have access to the database.
|