[18.0][MIG] hr_employee_calendar_planning: Migration to 18.0 #1419
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This module allows to manage employee working time with profiles by date intervals. The profiles are regular working time calendars, but they are treated as master ones here, allowing you to compose complexes working times by dates. Under the hook, a unique working time is created for each employee with the proper composition for not affecting the rest of the functionality linked to this model. Installation ============ During the installation of the module, current working times are split by start/end dates for having consistent data, and the potential new composed calendar planning is saved instead on the employee. Configuration ============= 1. Go to *Employees > Employees*. 2. Open or create a new one. 3. On the "Public Information" page, fill the section "Calendar planning" with: * Starting date (optional). * Ending date (optional). * Working time to apply during that date interval. Known issues / Roadmap ====================== * Add a wizard for generating next year calendar planning based on current one in batch. * Add constraint for avoiding planning lines overlapping. * Avoid the regeneration of whole private calendars each time a change is detected. [UPD] README.rst
[UPD] README.rst
[UPD] Update hr_employee_calendar_planning.pot
Add _description for model hr.employee.calendar to make it pass runbot. [UPD] Update hr_employee_calendar_planning.pot
[UPD] Update hr_employee_calendar_planning.pot [UPD] README.rst Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: hr-13.0/hr-13.0-hr_employee_calendar_planning Translate-URL: https://translation.odoo-community.org/projects/hr-13-0/hr-13-0-hr_employee_calendar_planning/
- On the module init, existing employee calendar leaves should be linked to the employee's new autocalendar. hr_employee_calendar_planning 13.0.1.0.1
[UPD] README.rst
[UPD] Update hr_employee_calendar_planning.pot [UPD] README.rst
Currently translated at 94.4% (17 of 18 strings) Translation: hr-14.0/hr-14.0-hr_employee_calendar_planning Translate-URL: https://translation.odoo-community.org/projects/hr-14-0/hr-14-0-hr_employee_calendar_planning/fr/
…r when is related to some employee [UPD] Update hr_employee_calendar_planning.pot hr_employee_calendar_planning 14.0.1.0.2 Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: hr-14.0/hr-14.0-hr_employee_calendar_planning Translate-URL: https://translation.odoo-community.org/projects/hr-14-0/hr-14-0-hr_employee_calendar_planning/
… field in to show only allowed records according to company. Add constraint to prevent change avoid changing the company when the calendar is linked to an employee of another company. [UPD] Update hr_employee_calendar_planning.pot hr_employee_calendar_planning 14.0.1.1.0 Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: hr-14.0/hr-14.0-hr_employee_calendar_planning Translate-URL: https://translation.odoo-community.org/projects/hr-14-0/hr-14-0-hr_employee_calendar_planning/
…even when calendar is not active. TT31606 [UPD] Update hr_employee_calendar_planning.pot [UPD] README.rst Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: hr-14.0/hr-14.0-hr_employee_calendar_planning Translate-URL: https://translation.odoo-community.org/projects/hr-14-0/hr-14-0-hr_employee_calendar_planning/
…weeks. Regenerate automatic calendar correctly when calendars are 2 weeks old (or any of them are 2 weeks old). TT32425
…r if calendars have been defined in employee creation. TT32425 [UPD] README.rst
Currently translated at 100.0% (22 of 22 strings) Translation: hr-14.0/hr-14.0-hr_employee_calendar_planning Translate-URL: https://translation.odoo-community.org/projects/hr-14-0/hr-14-0-hr_employee_calendar_planning/ca/
…void create employees without calendar planing. TT35897
hr_employee_calendar_planning 14.0.1.3.1 Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: hr-14.0/hr-14.0-hr_employee_calendar_planning Translate-URL: https://translation.odoo-community.org/projects/hr-14-0/hr-14-0-hr_employee_calendar_planning/
Parent is not necessary on context, this returns the next error when you try to select a calendar planning on the employee: ``Uncaught Error: NameError: name 'parent' is not defined`` hr_employee_calendar_planning 14.0.1.4.0
…to autogenerated calendar
Currently translated at 100.0% (23 of 23 strings) Translation: hr-14.0/hr-14.0-hr_employee_calendar_planning Translate-URL: https://translation.odoo-community.org/projects/hr-14-0/hr-14-0-hr_employee_calendar_planning/es_AR/ hr_employee_calendar_planning 14.0.1.4.1
…from employee public form view TT40038
Currently translated at 100.0% (23 of 23 strings) Translation: hr-15.0/hr-15.0-hr_employee_calendar_planning Translate-URL: https://translation.odoo-community.org/projects/hr-15-0/hr-15-0-hr_employee_calendar_planning/it/
Currently translated at 100.0% (23 of 23 strings) Translation: hr-15.0/hr-15.0-hr_employee_calendar_planning Translate-URL: https://translation.odoo-community.org/projects/hr-15-0/hr-15-0-hr_employee_calendar_planning/it/
We should only fill the calendar with sync_user if and only if you don't have one Sync user is used also when we modify the user of an employee
…have finished. Show them on calendar view
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: hr-15.0/hr-15.0-hr_employee_calendar_planning Translate-URL: https://translation.odoo-community.org/projects/hr-15-0/hr-15-0-hr_employee_calendar_planning/
…o cover all use cases TT44093
…calendar_id fields to allow removal TT44093
… by linking new leaves to auto-generated calendars on creation
…sheet in employee view
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: hr-16.0/hr-16.0-hr_employee_calendar_planning Translate-URL: https://translation.odoo-community.org/projects/hr-16-0/hr-16-0-hr_employee_calendar_planning/
Currently translated at 100.0% (24 of 24 strings) Translation: hr-16.0/hr-16.0-hr_employee_calendar_planning Translate-URL: https://translation.odoo-community.org/projects/hr-16-0/hr-16-0-hr_employee_calendar_planning/es/
Currently translated at 100.0% (24 of 24 strings) Translation: hr-16.0/hr-16.0-hr_employee_calendar_planning Translate-URL: https://translation.odoo-community.org/projects/hr-16-0/hr-16-0-hr_employee_calendar_planning/it/
Only create and unlink necessary resource_calendar_leaves
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: hr-17.0/hr-17.0-hr_employee_calendar_planning Translate-URL: https://translation.odoo-community.org/projects/hr-17-0/hr-17-0-hr_employee_calendar_planning/
This test collides with the dms module. In this test an employee is being created with a name that already exists in another test. The employee's file directory is created with the name of this employee. As there is already an employee with that name, there is already a directory with that name and this is what causes the error. As the probability of 2 employees with the same name coinciding in the same company is very small, instead of intervening in the logic for the creation of the employee's directory, we change the name of the employee in the test so that it does not cause the error when executing this module together with dms. In the hypothetical case of two employees with the same name within the same company, we would have to resort to using other tools, either by creating an additional module to modify the logic and add an employee identifier to the name of the directory. TT52110
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.