PURPOSE Make aliases usage more unique, prevent re-using bounce or catchall aliases and remove auto-uniqueness of aliases. SPECIFICATIONS Before this commit, user could create an email alias having same name as catchall/bounce email alias, which should not happen. Also, while creating or duplicating alias, if the same name was already available, a new unique name was generated by adding a sequence number to existing name. This behavior is not considered as a good one as it magically creates aliases different from what user expects. User could even not own the newly-created alias, leading to a broken mail gateway. In this commit we improve that behavior by ensuring that no duplicate alias name should be entered while creation / updation for both catcall/bounce and mail alias. Also, while duplicating an alias, name will now be blank by default to force user to enter the name. Finally when creating an alias an error is raised if the name is already taken. Task ID 2160070
* Code cleanup * Avoid a safe evaluation of the field value when loading those records. closes odoo/odoo#44883 Related: odoo/enterprise#8283 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
This reverts commit ff1c35513aecef5fbc30f7c2f3834450e719714e. closes odoo/odoo#41480 X-original-commit: 116057b26e71db4692280463669f3e80d813ddcc Related: odoo/enterprise#7110 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
FontAwesome 5 introduced new names for some icons as described on https://fontawesome.com/how-to-use/on-the-web/setup/upgrading-from-version-4#name-changes This commit replaces the old names to the new ones. closes odoo/odoo#35826 Taskid: 2050241 Related: odoo/enterprise#5180 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
The mail.message.subtype model contains a field internal, which decides if the messages are visible to external users or not. Such a value should not be overriden at module update, so all subtypes should be in noupdate. opw 1946043 closes odoo/odoo#32214 Signed-off-by: Nans Lefebvre (len) <len@odoo.com>
This field is a non-sense. By using the same logic, it should be added to any low level model. Replace the check by a simple verification of presence of an XMLID. A more generic opt-in solution should be integrated into ORM. Partially revert commits 0db0e66e96a8f6b393565da6fbb8dce25ec960b7 and bbd64c22abc19558c1d83a892fc426bf99a094ce. See #29257 odoo/enterprise#3550 closes odoo/odoo#31778 Signed-off-by: Christophe Simonis <chs@odoo.com>
Purpose of this merge is to update main addons and set activity types used for automated activities as master data. This means they cannot be removed. Indeed those activity types are used in business flow to generate activities and removing them may break some flows. This commit is linked to task ID 1907970 and PR #29257.
When a user is assigned as responsible of request, we want him to get a mail saying that he's a assigned to this request, a standard behaviour exists in Odoo to perform such a thing, which consist of having a field named 'user_id' which is tracked, so to avoid overriding the method, we renamed the field 'technician_user_id' in 'user_id'. Wre also set teh mail subtype 'request create' with default false, to have the same behaviour as the on in project, meaning that it is true only if you have the parent subtype set to true. TASK-ID: 58645