CopyClipboardJobLinkButton

A job posting has a public link, and the single most common thing anyone does with it is copy it to paste somewhere else. The base copy button handles that, confirming the copy by changing its own label for a moment.

On the recruitment form that confirmation is easy to miss, because the button sits among other controls and the label change is small. This widget replaces it with a notification.

Nothing else changes. The copy mechanism and the value read are both inherited, so the file exists purely to change how the copy is confirmed.

Confirmation of a copy sounds trivial until you watch someone click three times because they were not sure it worked, then paste three copies. Feedback that is impossible to miss is worth the twenty lines.

The wider point for recruitment is that the job link is the top of the funnel. Anything that makes sharing it slower or less certain costs applications, and this is the cheapest possible fix for one of those frictions.

The usual usage

<field name="job_link"
       widget="CopyClipboardJobLinkButton"/>

The capitalization is part of the registered name.

What differs from the base

# base: the button's own label changes briefly
# this: a notification confirms the copy

The copy itself is identical.

The base copy button

<field name="job_link" widget="CopyClipboardChar"/>

Same copy, with the label change instead.

The file is a subclass of the copy button with one method overridden: the one that runs after a successful copy.

Where the base changes the button's own label for a moment, this version shows a notification instead. The notification is a positive one, so it appears in the standard success styling rather than as a warning.

Everything upstream of that is untouched. The value read, the copy call and the failure handling all come from the base, which is why the whole file fits on a screen.

The capitalized registration is the only other thing worth noting, and it is a naming inconsistency rather than a design choice. It has to be written as registered because the registry lookup is exact.

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.

Byte-identical. The file on the development branch matches Odoo 19 exactly, including the capitalized registration.