task-2282334 closes odoo/odoo#56584 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
A mail alias is still linked with the res.users model with 2 fields, alias_id and alias_contact (related). It is not used anymore. We can therefore remove those fields. Aliases were added at 052f2ace57e20f06980bc8fadf37b32be1921420 . Purpose was to be able to discuss with users directly using Odoo as a mailbox. However it was not usable and was quickly deactivated. Aliases on res.users was removed at 029d1baf359eabb7ed531287f3cb2b3b8d586d39 . It was decided at that time to not support alias on users anymore as it was creating more issues than adding communication facility. This commit finally removes the unused fields. If necessary in some custom flow they can always be added through studio. LINKS Task ID 1919277 Community PR odoo/odoo#41160 Enterprise PR odoo/enterprise#6983 Upgrade PR odoo/upgrade#872 Co-Authored-By: Rémy Voet <ryv@odoo.com> Co-Authored-By: Thibault Delavallée <tde@odoo.com>
Improve the usability of the employees profile / "My Profile" TaskID: 2048672 closes odoo/odoo#35587 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
closes odoo/odoo#34931 Signed-off-by: Yannick Tivisse (yti) <yti@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>
Replace name 'out of office' group string from 'Out of Office' to 'Chat Status'. Replace 'out_of_office_message' field string from 'Out Of Office Message' to 'Message'. Task 1999697 closes odoo/odoo#33552 Signed-off-by: Martin Geubelle (mge) <mge@openerp.com>
This status can be edited by user in preferences, indicates if user is available or not.
Currently partners have a boolean field to choose whether to receive notifications only in their Odoo inbox or to receive them in their inbox and by email. This leads to several issues : * if a customer is configured to not receive emails he will not receive any notification on sales orders, leads, ... This is not clearly indicated to the salesman and it is not easy to know how to change that behavior * if an user chooses to receive emails and does not use its inbox a lot of notifications stay in Odoo. The user has to manually set them as done to make them disappear which is redundant. This commit changes that behavior. From now on customers will always receive all notifications by email. Indeed Odoo is not a customer oriented mailbox. Moreover sales orders or discussions on leads send to customers should always be sent by email as it is the standard communication mechanism. Users will be able to choose to receive notifications in Odoo or by email. The choice is no longer inbox or inbox + email, but inbox or email. Choosing one option or the other one depends on the way the user wants to work. Technically the field is moved on the users model and selection keys are renamed. Notification process is modified * notified_partner_ids contains as before specified recipients as well as followers matching the subtype * customers and users working with emails are notified. During that process customers notifications are marked as done to be able to track the email state without having needaction. Users notifications are currently deleted as we do not track their email state. The removal of partner field implies changes in various addons that define partner data with this field set in the values.
This commit remove required alias on res.users model. It also removes the inheritance of mail.alias.mixin. The field alias_id is kept and allow people to use aliases on users if they want. However there is no default void alias created for each user anymore. Default from of mail.message does not use user alias anymore. Indeed this creates issues with aliases not being correctly configured and can be confusing compared to private channels. Using user aliases is therefore now done manually instead of being a default behavior.