RomainLibert
f61687a4cd
Purpose ======= Have a clear distinction between leave and allocation requests instead of using the same model to mix 2 different concepts. Splitting the model will allow different business code to be run on each model as allocations and leaves are not exactly the same thing; this will add some code but simplify future improvements Specification ============= 1/ Completely separate the models Model hr.holidays has been split into leave.request and leave.allocation. 2/ Make reporting working again by using an SQL view aggregating data from leaves and allocations A new report has been added in order to aggregate datas from both allocations and requests. The views have been modified accordingly.
21 lines
891 B
Python
21 lines
891 B
Python
# -*- coding: utf-8 -*-
|
|
# Part of Odoo. See LICENSE file for full copyright and licensing details.
|
|
|
|
from . import models
|
|
|
|
|
|
def post_init(cr, registry):
|
|
""" Set the timesheet project and task on existing leave type. Do it in post_init to
|
|
be sure the internal project/task of res.company are set. (Since timesheet_generate field
|
|
is true by default, those 2 fields are required on the leave type).
|
|
"""
|
|
from odoo import api, SUPERUSER_ID
|
|
|
|
env = api.Environment(cr, SUPERUSER_ID, {})
|
|
for hr_leave_type in env['hr.leave.type'].search([('timesheet_generate', '=', True), ('timesheet_project_id', '=', False)]):
|
|
company = hr_leave_type.company_id or env.user.company_id
|
|
hr_leave_type.write({
|
|
'timesheet_project_id': company.leave_timesheet_project_id.id,
|
|
'timesheet_task_id': company.leave_timesheet_task_id.id,
|
|
})
|