[16.0][ADD] mail_message_view: list the chatter messages in a menu - #247
Open
smorita7749 wants to merge 1 commit into
Open
[16.0][ADD] mail_message_view: list the chatter messages in a menu#247smorita7749 wants to merge 1 commit into
smorita7749 wants to merge 1 commit into
Conversation
smorita7749
force-pushed
the
16.0-add-mail_message_view
branch
from
August 12, 2026 08:11
e15eb3e to
e0667aa
Compare
The chatter mixes the messages posted by users with the ones logged by the system, so following a long history is tedious, and the tracked field changes are only readable from the chatter itself, as tracking_value_ids is restricted to base.group_system. This module lists the messages in a dedicated menu, where they can be searched, filtered and grouped, with a plain text preview of the body and a summary of the tracked field changes. A button opening the same list for a single record can be added on the form views of the wanted models. Assisted-by: Claude Opus 5
smorita7749
force-pushed
the
16.0-add-mail_message_view
branch
from
August 12, 2026 11:08
e0667aa to
448c939
Compare
| _inherit = "mail.message" | ||
|
|
||
| document_name = fields.Char(string="Document", compute="_compute_document_name") | ||
| body_preview = fields.Char(compute="_compute_body_preview") |
Contributor
There was a problem hiding this comment.
Can't we use odoo standard field preview?
| class MailMessage(models.Model): | ||
| _inherit = "mail.message" | ||
|
|
||
| document_name = fields.Char(string="Document", compute="_compute_document_name") |
Contributor
There was a problem hiding this comment.
document_name shadows the stored record_name with an unstored compute, so the column can't be sorted, searched or grouped, and it costs a display_name read per model per page. The gap is real but it's a core inconsistency — message_post fills record_name while _message_log/_message_log_batch pass 'record_name': False, skipping the backfill in _message_create — so it's better closed by filling the field on create (batched per model) than by computing it on read.
yostashiro
reviewed
Sep 10, 2026
Member
There was a problem hiding this comment.
Please add yourself as a maintainer.
| </field> | ||
| <!-- The subject is empty on most of the chatter messages. --> | ||
| <field name="subject" position="attributes"> | ||
| <attribute name="optional">hide</attribute> |
Member
There was a problem hiding this comment.
Shouldn't we flip it to show?
| </field> | ||
| <field name="res_id" position="attributes"> | ||
| <attribute name="optional">hide</attribute> | ||
| </field> |
Member
There was a problem hiding this comment.
I think this will be useful.
Suggested change
| </field> | |
| </field> | |
| <field name="res_id" position="after"> | |
| <button | |
| name="action_open_document" | |
| type="object" | |
| icon="fa-file-text-o" | |
| title="Open Document" | |
| attrs="{'invisible': ['|', ('model', '=', False), ('res_id', '=', 0)]}" | |
| optional="show" | |
| /> | |
| </field> |
| @@ -0,0 +1,81 @@ | |||
| # License AGPL-3.0 or later (https://www.gnu.org/licenses/agpl). | |||
Member
There was a problem hiding this comment.
Suggested change
| # License AGPL-3.0 or later (https://www.gnu.org/licenses/agpl). | |
| # Copyright 2026 Quartile (https://quartile.co) | |
| # License AGPL-3.0 or later (https://www.gnu.org/licenses/agpl). |
Do the same to other files.
Member
|
@smorita7749 Can we rename the module to mail_message_history? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This module lists the chatter messages in a dedicated Discuss > Message History
menu, where they can be searched, filtered and grouped.
The chatter mixes the messages posted by users with the ones logged by the system
(field tracking, automated notifications), which makes a long history tedious to
follow. On top of that, the tracked field changes are only readable from the
chatter, as
tracking_value_idsis restricted tobase.group_system.The list therefore shows, as plain text, a preview of the message body and a
summary of the tracked field changes, e.g.
Status: RFQ -> Purchase Order, andprovides filters telling the messages posted by users apart from the ones logged
by the system.
Notes:
mode), so the standard Messages list is left unchanged;
models listed in the
mail_message_view.button_modelssystem parameter;document is an expensive query.
Targeting 16.0 as this is the series where the module is used, but I am happy to
forward-port it first if maintainers prefer new modules to land on the latest
branch.
This is a new module of about 1000 lines, which is above the 500 lines of the OCA
metrics red lines. Please let me know how you would like to proceed with the
review.
Assisted-by: Claude Opus 5
@qrtl QT7086