hr_holidays_radio_image

Each Time Off type in Odoo carries a cover image: the small illustration that identifies Paid Time Off, Sick Time Off or Parental Time Off wherever the type appears. Choosing that image on the type's form is not a file upload and not a dropdown. It is a row of pictures, and you click one.

Underneath, it is the ordinary radio widget. The only thing this widget changes is the template: instead of a label next to each radio input, it renders an image, and the source of that image is the option's own label. The label goes straight into a URL under the module's icons folder.

In core the field is a many2one to ir.attachment, restricted by domain to attachments whose model is the Time Off type and whose field is this one. The eight shipped icons are seeded as URL-type attachment records whose names are the SVG file names, which is what makes label-as-file-name work.

Icons on time off types are not decoration. They appear on the Time Off dashboard where employees pick what to request, and a recognizable picture removes a class of mistake that plain text does not: requesting sick leave when you meant unpaid, or the wrong one of three similarly named allowances. For a company with more than a handful of types, that is worth the two minutes of configuration.

The practical constraint is that the choice is limited to what the module ships. Adding your own illustration means adding an attachment record with the right model and field, and putting a matching image where the widget expects to find it. That is a small technical task, not a configuration screen, and it is worth knowing before promising a client branded leave icons.

The larger planning point is the Odoo 20 direction. On the development branch the Time Off type model itself is folded into work entry types, and this picker, its icon attachments and the form section that held it all disappear together. If leave type icons are part of a design you are committing to, treat them as version-bound.

The core usage

<field name="icon_id" widget="hr_holidays_radio_image"
       class="o_time_off_icon_types d-flex flex-wrap"
       options="{'horizontal': true}"/>

Straight from the Time Off type form. The horizontal option is passed and then ignored by the replaced template, so core ships a no-op here.

The field it sits on

# hr_leave_type.py
icon_id = fields.Many2one('ir.attachment', string='Cover Image',
    domain="[('res_model', '=', 'hr.leave.type'),
             ('res_field', '=', 'icon_id')]")

The domain is what limits the row to the shipped icons. Widen it and the widget will happily try to render whatever comes back.

Adding your own icon

<record id="icon_custom" model="ir.attachment">
  <field name="name">Study_Leave.svg</field>
  <field name="res_model">hr.leave.type</field>
  <field name="res_field">icon_id</field>
  <field name="public" eval="True"/>
  <field name="type">url</field>
  <field name="url">/hr_holidays/static/src/img/icons/Study_Leave.svg</field>
</record>

This mirrors how core seeds its eight icons. The record's name has to match the file name, because the widget builds the image URL from it.

The JavaScript is four meaningful lines: subclass the radio field, point it at a different template, register it with the unchanged radio descriptor. Everything interesting is in the template.

The base radio widget exposes its choices as pairs. For a selection field the pair is value and label; for a many2one it is id and display name, fetched by the widget's own search. The template here takes the second element of that pair and drops it into an image source under the module's icons folder. So on a many2one, the record's display name becomes the file name, which is exactly why the shipped attachments are called Paid_Time_Off.svg rather than Paid Time Off.

Read-only mode is written differently from edit mode and is the fragile half. It guards against no value at all, then finds the matching pair and reads its second element. If the stored value is not in the fetched list, for example because the field's domain changed or the attachment was deleted, that search returns nothing and reading from it raises. Edit mode has no such problem, since it simply renders the whole list.

The inherited horizontal option is the other verified detail. The base template consumes an orientation prop; this template does not, laying the images out with fixed flex-wrap classes instead. The extractor still produces the prop, so the option is accepted, passed and ignored, and core's own view passes it. Its sibling in the HR module, hr_homeworking_radio_image, has exactly the same dead option.

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

The widget is deleted. Its JavaScript and template files are absent from the development branch, and so is its only usage, because the Time Off type form is gone: on that branch hr_leave_type.py and hr_leave_type_views.xml no longer exist and the model is folded into work entry types, which the same module now extends.

The icons go with it. The data file that seeded the eight cover-image attachments is also absent, and the field itself does not reappear on the replacement model. This is not a rename, it is a removal, and it follows the same path taken by the sibling hr_homeworking_radio_image widget, which is also deleted on that branch.

Anything in a custom module that references this widget, the Time Off type icons, or the type form section that holds them should be treated as work to be redone rather than migrated.