[19.0][OU-ADD] im_livechat: chatbot_only_if_no_operator → chatbot_enabled_condition

[dnplkndll]

Summary

19.0 replaces the boolean im_livechat.channel.rule.chatbot_only_if_no_operator with a selection field chatbot_enabled_condition (always / only_if_no_operator / only_if_operator).

Migration

• pre-migration.py — openupgrade.rename_columns to preserve the legacy boolean column past ORM init.
• post-migration.py — UPDATE im_livechat_channel_rule SET chatbot_enabled_condition = 'only_if_no_operator' WHERE <legacy column> IS TRUE. FALSE rows keep the ORM-set default of always.
• Legacy column preserved for database_cleanup to pick up post-migration (per pedrobaeza policy on OpenUpgrade preserving information).

Test coverage

openupgrade_scripts/scripts/im_livechat/19.0.1.0/tests/test_im_livechat_migration.py:

1. asserts at least one channel.rule has chatbot_enabled_condition='only_if_no_operator' after migration
2. asserts the legacy column still exists in the schema (so database_cleanup can clear it)

openupgrade_scripts/scripts/im_livechat/tests/data_im_livechat_migration.py — 18.0 demo seed: sets chatbot_only_if_no_operator=True on at least one channel.rule so the post-migration UPDATE has rows to fire on.

What this PR does NOT touch

Per pedrobaeza policy ("OpenUpgrade preserves information; database_cleanup handles residuals"), these 19.0 changes in im_livechat are intentionally left alone:

• Additive new tracking fields on discuss.channel (auto-populate at ORM init)
• New models: im_livechat.channel.member.history, conversation.tag, expertise (additive)
• DEL fields anonymous_name, livechat_active, image_128, input_placeholder — left for database_cleanup

Fork CI

Validated on fork's `Test OpenUpgrade migration` workflow (both base + enriched seeds passed): 2026-05-16T01:58Z.

docsource

docsource/modules180-190.rst updated — `im_livechat` marked Done so OCA CI's `Test OpenUpgrade migration` job includes the module in `$MODULES_NEW`.