RomainLibert
e0b16b22e8
Purpose ======= Having a clean policy in leave access right. If there are some internal need or bugs, read this before decided if it is an expected brhavior or not. It is what we want in a standrard point of vew. Specification ============= Access rights Policy -------------------- Remove Time Off - Team Leader access right Leave_manager_id is now requried, by default it is = parent_id for admin it is admin by default (data employee_admin) 3 access rights: - Internal User - Time Off - All Approver - Time Off - Administrator 3 fields for "manager" - parent_id - leave_manager_id - manager_id on department Department Is just there for information. So never use it in default filters Rules Policy ------------ Don't forget to take the leave type configuration into account * no validation means automatic * officer validation means you need to be at least holidays_user to approve * manager validation means anyone who is at least leave_manager_id can approve Internal User ------------- In double validation mode he: - can only do the first approval - can see the everyone's leaves with a anonymisation of the leave description - can create a leave (even if leave type is directly approved) - can refuse its own leaves (till not reported in payslip) - can reset to draft his own leaves and reconfirm them - can delete a leave in draft state - can cancel a leave if the date_start is in the future - cannot validate its own leaves If leave type is configured in manager mode, he: - can approve or refuse the leaves if he is leave_manager_id If leave type is configured in both mode, he: - can only do the first approval or refuse for the leave if he is leave_manager_id Time Off - All Approver ----------------------- In double validation mode he: - can only do the second approval - can see, write, read all leaves and perform the second approval. - Can set a leaves as reported in payslip. - Cannot validate its own leaves - cannot configure leave type - cannot create leaves in batch Time Off - Administrator ------------------------ In double validation mode he: - can do all the approvals - can bypass all leaves (approve or refuse). - can configure Time Off Types - can create batch leaves - can validate its own leaves Menu ---- - My Time Off (access rights: internal user) - Dashboard - Time Off Requests - Allocation Requests - My Team (rename into "Everyone", access rights: internal user. default filters on current year and group by employee; default view: gantt can switch to list and form) - Managers - To Approve (internal user who are leave_manager_id see and can approve. See only leave he has to approve (domain)) - Time Off - Allocation - All - Time Off - Allocation - Payroll - Time Off to report. - Reporting (access right: time off administrator) - Time Off Analysis - Report by Department - Configuration (access right: time off administrator) Usability --------- - In all list of "manager menus", add actions to change status in mass - In leave type data: - move Home Working from data to demo data - There are 2 Paid time off, get rid of the company on it and share it on all companies (keep only the one in data) - Leave type like this: - Overtime Compensation/compensatory days (keep only one of both, to avoid having 2 same leaves in demo data). Validation by: team leader and hr officer, no validity date - Paid Time Off 2019. Validation by Team Leader and Payroll Officer. Remove validity, remove 2019. - Unpaid. Can be taken in hours. Approved by Payroll officer and team leader. No allocation needed. - New leave request: order of leave type in the m2o: 1. leaves where allocation are fixed by rh and remaining > 0 and allocated > 0 2. leaves where free allocation. Where reaming is > 0 and allocated >0 3. One already taken 4. All other leaves. - Remove the sequence widget in leave type - The employee should get a notification when his leave is refused "Your "leave_type_name_" planned on "start_date" has been refused" - from the dashboard calendar, the reset to draft should lead to edit (avoid user has to click on edit) - An employee should be notified when a leave is approved "Your [leave_type_name] on [start date] has been approved" Leave Dashboard V2 ------------------ https://drive.google.com/file/d/1pMCqDlecqM7ngvmhJJdWtkG2_GiXHyIX/view?usp=sharing Testing ------- Everything concerning the leave requests has to be tested. All the access rights have been reviewed and need testing. Migration --------- Don't forget to keep the filters in the calendar view (otherwise RIP perfomances and usability) TaskID: 1950998 closes odoo/odoo#33813 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
Odoo
Odoo is a suite of web based open source business apps.
The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Warehouse Management, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, Purchase Management, ...
Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
Getting started with Odoo
For a standard installation please follow the Setup instructions from the documentation.
Then follow the developer tutorials