Make the employee presence icons more descriptive. Allow to quickly filter the Presence Reports based on the user status. closes odoo/odoo#54527 Taskid: 2246447 Related: odoo/upgrade#1488 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
closes odoo/odoo#45677 X-original-commit: 9506581eb221ed709acaabcb5544e1cf6effb7f1 Signed-off-by: jbm-odoo <jbm-odoo@users.noreply.github.com>
This will improve the extendibility of view inheritance closes odoo/odoo#41398 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
1/ web: adapt formatDate to handle NaN values DashboardRenderer might return NaN for `Date` or `DateTime` fields if their original value is null or incorrect. 2/ hr: add job_title in demo data 3/ hr_recruitment: link employee in the chatter for new recruits 4/ hr: remove employee documents in the model 5/ hr_attendance: improve resiliency of relative_time 6/ hr: display manager on res_users 7/ hr: change Address Book to Employee Directory TaskID: 2009111 closes odoo/odoo#34180 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
Purpose ======= There are currently multiple ways to determine if an employee is presence or absent: - login state (user status on chat) - checkin/checkout from the Attendance app - leave - hr_presence (email, ip) Those states are displayed in several different places and can be inconsitent. e.g. Logged in -> green in the chat Not checked in -> red on the employee kanban view. The multiple ways to determine employee presence described above should be aggregated together to have a better consistency. Specification ============= There are 3 presence states (previously defined in module `hr_presence`), namely `present`, `absent`, `to_define`. They are now defined as soon as `hr` module is installed. The state computation can have several behaviors according to which apps are installed: 1. `hr` is installed Check employee presence based on login by default (only for employees with a user). Kanban state (private and public): should be green when logged in, red when logged out and orange when the user is away. Private employee form: Display a stat button "Connected" on the form view when the user is logged in or "Last Activity xx/xx/xxx" otherwise. 2. `hr_attendance` is installed: when the user is logged out, the state is determined from the checked in/out state. But when the user is logged in, consider the user as present (even if he checked out). Kanban state: green for checked in, red for checked out Private form view: attendance stat button. 3. `hr_holidays` is installed: Has the highest priority if the employee is on leave. Kanban state: red if employee is on leave. Private form view: stat button "Absent Until xx/xx/xxxx" if employee is on leave. 4. `hr_presence` is installed: Two additionnal presence checking option: emails sent and IP address connected. Once a user sent an email or the IP address was connected, he is considered present for the entire day. There should be at most one stat button on the employee form view, with the relevent information. Task id: 2024482 closes odoo/odoo#34933 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
Purpose ======= While cleaning the stat buttons across all modules, we decided to move the (un)archiving from stat button to actions in the 'Action' dropdown. Specification ============= Remove the 'active' stat buttons in all views
* attendance, contract, fleet, holidays, maintenance, presence, timesheet. For the model 'hr.employee', replace the actions menu 'Archive/Restore' by the stat button. That's why adapted changes regarding xpath. Also rename the actions menu 'Time Off' by 'Time off'. Linked to task 1984526 Related to PR #33720
Commit d77ce4c introduced a new inherited kanban view for employees. However an other kanban used the same xmlid. Only one is loaded. This commit changes the xmlid for the new kanban view. closes odoo/odoo#32567 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
General Purpose =============== We want an 'Employee profile' gathering every data about an employee. The main form view is modified to become this employee profile. A user can also see his own profile through the Preferences menu. The new profile replaces the current Preferences view if the hr module is installed and the current user is linked to an employee. A user should be able to see and edit his own profile. *Problem*: Many fields on hr.employee are protected by groups="hr.group_hr_user". Therefore, a regular user cannot see or edit those fields. This protection must be bypassed to allow read/write access to the regular user's own data. A similar mechanism already exists for res.users (for Preferences) The better (least worst) solution found is to reuse this mechanism by adding related fields on res.users. Pros: - Don't change security access on hr.employee - Don't implement yet another custom security layer, risking to add new security breaches - A lot of fields are added by other modules on hr.employee. It would have required to integrate them with the custom security layer. - Fields added by other modules on the user's preferences view (normal view, not the profile) are automatically included in the employee's profile view. - Allow the hr.employee form view to be different than the user profile accessible through the Preferences menu. E.g. add custom buttons only relevant to the logged in user such as "Request a leave". Cons: - Each field from hr.employee that you want to appear on its profile must be added as a related field on res.users - Those related fields must be added to user's preferences view (duplicate views) - They also must be added to SELF_[READABLE | WRITABLE]_FIELDS Note: When the front-end loads the views it gets the list of available fields for the user (according to its access rights). Later, when the front-end wants to populate the view with data, it only asks to read those available fields. However, in this case, we want the user to be able to read/write its own data, even if they are protected by groups (groups are kept on the related fields on res.users). The front-end need to be made aware of those fields by sending all field definitions. hr_attendance ============= This commit integrate attendance in the new employee profile. It also adds a stat button to this employee profile showing the number of hours worked last month. Remove the boolean computed field 'manual_attendance'. This field is just a shortcut to add/remove the employee's user in the "Manual Attendance" group. The checkbox is confusing on the employee's form and this should be done through the normal group management screens. hr_presence =========== Display the presence status on the employee kanban template. The status is a colored chip which can be green (present), orange (to define) or red (absent). Currently, the presence status is only computed when accessing the report view. As this commits displays it on the employee kanban, it should be updated more frequently. The state should not be updated every time the kanban view is loaded since the computation is a bit heavy. Instead: add a cron to update status every 15 minutes. -> The status is accurate on the report view (status is still updated when loading the view) -> The status in accurate at 15 minutes on the kanban view [ADD] hr_attendance_presence ============================ Bridge module between hr_attendance and hr_presence. This commit integrates hr_presence module in the employee profile and adds the presence status on the employee kanban view. But hr_attendance adds at the same place a similar status icon for checkin/checkout. This bridge module makes the status from hr_presence invisible as hr_attendance should be the main presence control mechanism. Also, this commit adds the ability (through a new setting option) for hr_presence to take into account checkin/checkout to determine the presence status. l10n_be_hr_payroll ================== integration with employee profile
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