Chatter Diff Tracking

See exactly what was removed and what was added — right in the chatter.

Why you need it

Odoo's standard field tracking logs the old and the new value side by side. That works for a date or a status — but for a long description, a rich-text policy, or a block of Python code it gives you two walls of text and a game of "spot the difference". Auditors, quality managers and reviewers waste time re-reading entire paragraphs to find one changed word.

Chatter Diff Tracking replaces that with a colored diff, the way developers review code: deletions in red strike-through, insertions in green, unchanged content left as is. One glance tells the whole story — perfect for ISO 9001 / QMS audit trails, legal texts, SOPs, product descriptions and configuration code.

Three renderers, picked automatically

Example

Posted automatically as an internal note — followers are not spammed with notifications.

For developers: two lines to adopt

Inherit the mixin next to mail.thread and flag any Char, Text or Html field:

class ProductPolicy(models.Model):
    _name = 'product.policy'
    _inherit = ['mail.thread', 'tko.diff.tracking.mixin']

    policy_text = fields.Html('Policy', diff_tracking=True)        # auto: html diff
    notes = fields.Text('Notes', diff_tracking=True)               # auto: text diff
    compute_code = fields.Text('Code', diff_tracking='code')       # unified diff
    legacy_html = fields.Text('Legacy', diff_tracking='html')      # force html diff

• No stored data, no new tables — diffs live in the chatter you already have.
• Multi-record writes supported; nothing is posted when the value did not actually change.
• Skip logging on demand with with_context(skip_diff_tracking=True).
• User content is always escaped — safe against markup injection.
• No external Python dependencies beyond what Odoo already ships.

TKOpen

Built and battle-tested inside our ISO 9001 QMS suite.
Questions or feature requests? tkopen.com