internal_resume_lines

Odoo 19 reworked employee records around versions: every contract change, job change or timeline event is an hr.version row. internal_resume_lines is the widget that turns that raw history into something people actually read, an automatic Experience section on the resume tab, listing the employee's roles at your company with start and end dates, current role marked Current.

It is a view widget with no options and no value of its own. On mount it calls a single server method, get_internal_resume_lines, and renders the returned entries as a timeline styled like a grouped list, headed by Experience and the company name. The editable resume lines, the resume_one2many field widget, sit directly beneath it in both core placements.

Manual resume upkeep is the first thing HR teams abandon. Titles change, promotions happen, and the resume tab quietly rots. This widget removes the internal half of that chore: as long as versions are maintained, which payroll and contracts force anyway, the employee's in-company career writes itself. Only external history, previous employers and education, still needs manual entry below.

The dual placement matters for self-service. The same block renders on the user's own profile form, so employees see their computed career path without HR access, and the underlying access check through the public employee model keeps it safe to expose.

How core places it

<!-- Adding fields in the list arch below makes them accessible to the widget -->
<widget name="internal_resume_lines"/>
<field mode="list" name="resume_line_ids" widget="resume_one2many"/>

From hr_skills/views/hr_views.xml. The widget needs no configuration; the pairing with resume_one2many is convention, not requirement.

The server call it makes

self.env['hr.employee'].get_internal_resume_lines(res_id, res_model)
# res.users ids are mapped to their employee first
# raises AccessError without read access to hr.employee.public

The interesting logic is all server side, in hr_skills/models/hr_employee.py. The method walks the employee's version_ids in order and emits one entry per contiguous stretch of the same job title, computing each stretch's start as the later of the version date and the contract start, and its end from the next version's date or the contract end. Versions without a job title close the running interval, and gaps between contracts split entries, so a rehire shows as two stints. The entries carry the version's id, job title and the date pair, nothing else, which is exactly what the template prints.

Client side, two details are easy to miss. The dates are formatted through Odoo's locale-aware formatDate, so the timeline follows the user's date format. And the empty-state paragraph, there are no resume lines on this employee, is gated by haveResumeLines, which is true if either the computed internal lines or the manual resume_line_ids have content, so the hint disappears as soon as anything at all is on the resume.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. We read the widget's file on the public development branch at the time of writing; the branch is unstable and this page will be re-verified after release.

The component is rewritten onto asyncComputed: the resume lines become reactive state with an initial empty array, recomputed automatically when the record changes, replacing 19's onWillStart and onWillUpdateProps pair, and internalResumeLines becomes a callable in the template. Registration, dependencies and the server method contract are unchanged, so only JavaScript patches are affected.