odoo-addon-mail-block-user-assigned-message 18.0.1.0.0

Configuration

To configure this module, you need to:

1. Go to the “Preferences” tab in an internal user.

2. Activate the “Block Assigned Message” option.

3. Select the models for which assignation notifications don’t have to be generated.

It is important to keep in mind that automatic assignment notifications are only created when a model meets the following requirements:

• The model is subclass of the abstract class mail.thread.

• The model has a user_id field.

• The tracking parameter of the user_id field is different to False.

This module will not work with models that do not meet all those three requirements. Also, notification methods can be overriden, so the module would not work in those cases either.

A particular example of a model that does not work is the project.task model. It does not have a user_id field, but a Many2many user_ids field. Assignment notifications are created using a specific custom method for this model, so are not blocked using this module.

Usage

To use this module, you need to:

1. Go to a model that has assign notifications. For example: res.partner (install the contacts module if you do not have the menu)

2. Login with a user that has permissions in that model with another browser or incognito mode. Create that user before if it does not exist

3. With the second user, assign a record to the first user selecting him on the user_id field. In our res.partner example, we will assign the first user as ‘Salesperson’.

4. The first user will not receive the assignation notification if you have configured them to be blocked in that model. You can also review if the notifications are correcly received without this block.

Note: Notifications are, by default, handled by emails. You can change them, to be handled in odoo, in your preferences.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits