0acd2251e6
The "My Schedule" portal page read only published planning.slot (Odoo Planning), but team leads post in the fusion_clock Shift Planner, which writes fusion.clock.schedule -> so posted schedules never appeared. Merge both sources: the page now lists published planning.slot AND posted fusion.clock.schedule (employee, state=posted, not OFF, within the 60-day horizon), sorted together. Verified on entech: Garry's 7 posted shifts (Jun 1-7) now render. 19.0.1.5.0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
43 lines
1.2 KiB
Python
43 lines
1.2 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2026 Nexa Systems Inc.
|
|
# License OPL-1 (Odoo Proprietary License v1.0)
|
|
# Part of the Fusion Clock product family.
|
|
|
|
{
|
|
'name': 'Fusion Planning',
|
|
'version': '19.0.1.5.0',
|
|
'category': 'Human Resources/Planning',
|
|
'summary': 'Fusion Clock bridge to Odoo Planning - employee schedule on the portal',
|
|
'description': """
|
|
Fusion Planning
|
|
===============
|
|
|
|
Adds Odoo Planning to the Fusion Clock product family:
|
|
|
|
* Adds a "My Schedule" tab to the Fusion Clock portal
|
|
* Reuses Odoo Planning's exact backend UI (Gantt, send wizard, recurrence)
|
|
* Bridges planning.slot with fusion_clock attendance and leave
|
|
""",
|
|
'author': 'Nexa Systems Inc.',
|
|
'website': 'https://nexasystems.io',
|
|
'license': 'OPL-1',
|
|
'depends': [
|
|
'planning',
|
|
'fusion_clock',
|
|
],
|
|
'data': [
|
|
'views/planning_slot_views.xml',
|
|
'views/hr_employee_role_views.xml',
|
|
'views/portal_schedule_templates.xml',
|
|
'views/portal_nav_inherit.xml',
|
|
],
|
|
'assets': {
|
|
'web.assets_frontend': [
|
|
'fusion_planning/static/src/css/portal_schedule.css',
|
|
],
|
|
},
|
|
'installable': True,
|
|
'auto_install': False,
|
|
'application': False,
|
|
}
|