This module adds the cities at the public vacation line level as an extra discriminant.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets you restrict each public holiday to specific cities, so employees only get holidays that apply to their city (or holidays with no city set).
This module adds a "Related Cities" field to public holiday lines, so a public holiday can be limited to one or more cities instead of applying to everyone.
Where it appears: - On the public holiday form, the new city field appears right after the states field, with a filter that only shows cities from the selected country and states. - When a holiday is created in the calendar, the city names are added to the event description.
Business rules and automatic behaviour: - When Odoo looks for public holidays for an employee, it uses the city on the employee's address; if the employee has no city, it falls back to the company's city. - A holiday applies if its city list is empty (applies everywhere) or contains the employee's city. - The same city rule is used when checking for unusual days on a leave request. - Changing the cities on a holiday line re-runs the date/state checks and updates the linked calendar event.
Areas touched: public holidays (calendar.public.holiday and its lines), leave requests (hr.leave), and calendar events created from holidays.
Depends on
Models and fields (3)
- hr.leave · extends an existing model
- calendar.public.holiday · extends an existing model
- calendar.public.holiday.line · extends an existing modelcity_ids
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 5 confirmed, 4 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/hr-holidays.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.