mail_activity_mixin_list_reschedule_dropdown

An activity that is overdue usually needs one of three answers: today, tomorrow, or next week. Opening the reschedule dialog to pick one of three dates is more ceremony than the decision deserves.

These two widgets are a small dropdown offering exactly those three, computed from the current date so the labels read as weekday names rather than as dates. Choosing one calls a server method that moves the activity.

After the call the whole list is reloaded, because rescheduling changes which records match the filter that produced it.

Activity backlogs are the quiet failure mode of a CRM. They build up because rescheduling costs more effort than ignoring, and once a list is mostly overdue nobody reads it at all.

Three-click rescheduling directly attacks that. It is worth pairing with a rule about what a next week deferral means, because the widget makes deferring as easy as doing.

Placing it

<widget name="mail_activity_mixin_list_reschedule_dropdown"/>

Inside a list of leads, tasks or similar.

What differs from the parent

# three method names, replaced after super setup
action_reschedule_my_next_*

Everything else is inherited.

The activity list variant

<widget name="mail_activity_list_reschedule_dropdown"/>

For lists of activity records themselves.

The three labels are computed at setup from the current date: today's weekday name, tomorrow's, and the first day of next week. That means the dropdown reads as weekday names, which is easier to act on than a date.

Each entry carries the name of a server method rather than a date. That is the important design choice: the browser never computes a target date, it names an intent and lets the server decide what today, tomorrow and next week mean given working days and calendars.

The action is dispatched as an object button against the record, with a close handler that reloads the list root and notifies the model. Both are needed: the reload fetches the new state, and the notification makes the list redraw.

The two registrations share a listing width hint of fifty to one hundred, which is what stops the dropdown column from claiming space it does not need.

The mixin variant differs in one respect only. It overrides the three method names after calling the parent setup, pointing at the my next variants, because on a business record the target is the user's own next activity rather than the activity record itself.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable and this may still change; we re-verify this page after the release.

Converted to newer conventions. The development branch updates the shared file to the newer props and dropdown conventions. The method name override is unchanged.