Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[16.0][MIG] hr_employee_calendar_planning #1290

Merged
merged 54 commits into from
Nov 27, 2023

Conversation

jonasbuchholz
Copy link
Contributor

Module migration, since there hasn't been any activity on #1242 for some time. Includes the commits mentioned by @victoralmau and a fix for the bug when creating new employees. For better formatting, the calendar_ids field is placed in a separate notebook page in the employee view

pedrobaeza and others added 30 commits November 7, 2023 12:49
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] 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] 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
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
etobella and others added 9 commits November 7, 2023 13:01
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
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/
@jonasbuchholz jonasbuchholz force-pushed the 16.0-mig_hr_employee_calendar_planning branch from 8085dae to d6d91d6 Compare November 7, 2023 16:40
Copy link
Member

@victoralmau victoralmau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some comments:

  • It is not clear to me that adding the calendars on a new page could not have side effects.
  • Check the tests and make the necessary fixes.

… by linking new leaves to auto-generated calendars on creation
@jonasbuchholz jonasbuchholz force-pushed the 16.0-mig_hr_employee_calendar_planning branch from d6d91d6 to 16c87e5 Compare November 15, 2023 17:33
<field name="inherit_id" ref="resource.resource_calendar_form" />
<field name="arch" type="xml">
<notebook position="inside">
<page name="employee_calendar" string="Employee Calendars">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding a new tab doesn't quite convince me, maybe you could move employee_calendar_ids field to another place (inside the tab it was previously in) to be the full size of the tab. What do you think @pedrobaeza ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, a whole new tab just for this seems over-killing.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think about leaving the label and setting a colspan? Looks like this:
employee_calendar_planning_form

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems it overflows a bit the limits.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I know what you mean. But to me, this seems like the way Odoo is treating fields like this in views, see eg here. Defining custom css just for this view seems a bit unnecessary. Alternatively, we could place it in a sheet, like this:
image

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, that can be another option.

@jonasbuchholz jonasbuchholz force-pushed the 16.0-mig_hr_employee_calendar_planning branch from 16c87e5 to 8576705 Compare November 27, 2023 09:03
@pedrobaeza pedrobaeza changed the title [16.0][MIG] hr employee calendar planning [16.0][MIG] hr_employee_calendar_planning Nov 27, 2023
Copy link
Member

@pedrobaeza pedrobaeza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/ocabot merge nobump
/ocabot migration hr_employee_calendar_planning

@OCA-git-bot OCA-git-bot added this to the 16.0 milestone Nov 27, 2023
@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 16.0-ocabot-merge-pr-1290-by-pedrobaeza-bump-nobump, awaiting test results.

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@OCA-git-bot OCA-git-bot merged commit e14fe86 into OCA:16.0 Nov 27, 2023
6 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 3cc2e3e. Thanks a lot for contributing to OCA. ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.