PURPOSE
=======
When you close a payroll (employees), there are often a lot of document
linked. Archiving an employee should archive the contract, cancel future
leaves, archive the private address
Specification
=============
Add departure date (hr):
- Add a Date field to both hr.departure.wizard and hr.employee. In
the wizard, the field is required.
- In toggle_active() method in hr.employee, set departure_date to
false when unarchive the employee.
- If user has a current running contract, a user error will raise if
user enter a departure date earlier than the start date of the
contract.
Add checkbox to set a closing date on hr.contract (hr.contract):
- In the hr.departure.wizard, set the departure date to be the end
date of runing contract. Set the states of all draft contracts to
"cancel".
Add checkbox to free car (hr.fleet):
- In the hr.departure.wizard, set end_date to
fleet.vehicle.assignation.log, if there is no end_date or end_date >
departure_date
- Go through fleet.vehicle, find records with dirver_id to be the
employee, set it to False.
Add checkbox to archive private address (hr):
- when the private address not link to a internel user, set
employee.address_home_id.active to Flase
- unarchive it after the employee unarchived
Add checkbox to cancel future appraisals (hr.appraisal)
- find all appraisals link to the employee and state in
['new', 'pending'], set their state to 'cancel'.
Add checkbox to cancel future leaves (hr.holidays):
- only consider leaves are not in state ['refuse', 'cancel'],
find leaves with to_date > departure_date, set their state to
'cancel'.
PR #42526
Task 2153106
Related: odoo/enterprise#7471
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
TaskID: 2053585 closes odoo/odoo#35737 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
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>
Multi is the default api for methods, it is not necessary to explicitly decorate methods with it, adds clutter and most people use it because they see that the rest of the code uses it. Done with `find . -type f -name '*.py' | xargs sed -i '/@api.multi/d'`
The old tree views don't really exist anymore, this odd pseudo-flag to dispatch between "list" and "tree" tree views has no reason to remain. Task 1937686 closes odoo/odoo#31243 Signed-off-by: Xavier Morel (xmo) <xmo@odoo.com>
Purpose ======= We need to use an international word to define holidays and leaves, rename everything into Time Off. Employees needs a good dashboard and leaves summary Specification ============= 1/ Add a new dashboard: https://balsamiq.cloud/sm5j0d/pg5w04r Create a new dashboard with a calendar and a summary of all time off and time off request 2/ Rename leaves into Time Off everywhere 3/ Improve general usability TaskID: 1916871 closes odoo/odoo#29634
It seems specifications of new menus implemented at 9af6e9070af1a949d3ec40a0767d2aa4ffc9719d were not totally correct and broke some Odoo conventions. New specification for leaves application menus are now the following : * Dashboard * My leaves (user sees this only) * New request (calendar view by default) * Leaves requests (only my, list view by default) * Allocation requests (only my, list view by default) * Summary (only my, summary list view by default) * Managers (HR officers or managers only) * To approve * Leaves (default filters: to approve, on my department) * Allocations (default filters: to approve, on my department) * All * Leaves * Allocations * Payroll * Leaves to report (default filters: grey kanban state) * Reporting (HR officers or managers only) * Leaves Analysis * Report by Department * Configuration * Leaves Types This commit is linked to task ID 1876795 and PR #26571.
BS4 "btn-default" class was replaced with "btn-secondary", which makes more sense.
Many error messages are misleading or too "vague" This task aims to improve all error message. Task #47042 PR #23321
When calling the function report_action from write_company_and_print_report, it failed because all the required data from the transient model "hr.holidays.summary.dept" were lost. opw:803051