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

[FIX] Modify how employee attedance is computed #19

Open
wants to merge 76 commits into
base: 16.0-mig-project_forecast_line
Choose a base branch
from

Conversation

QuiJoQuim
Copy link

The employee's attendance calculated the days differently by the total hours than by the distribution.

This resulted in attendances of 40.39 hours in 3 months and things like that.

This PR corrects this behavior.

yankinmax and others added 30 commits March 6, 2024 10:20
in some cases, we could have capacity consumed by a task which was not matching
a work capacity line in the period because of a faulty optimisation we were making
which skipped the creation of lines with a capacity of 0 -> then we had no line on which
to compute the negative consolidated capacity.

We remove the optimisation to fix this case and show the problematic periods
in the consolidated capacity graphs
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: project-15.0/project-15.0-project_forecast_line
Translate-URL: https://translation.odoo-community.org/projects/project-15-0/project-15-0-project_forecast_line/
During some operations, forecast lines are deleted and recreated. This
can lead to some hr.employee.forecast.role lines being deleted which
leaves the forecast lines on the same period without a related document
to store the consolidated capacity. Normally that line is recreated
shortly afterwards but the creation does not recompute the link between
the parent-less lines and the new one. This patches forces the
recomputation when new lines are created.
The idea is to have two consolidated forecast fields, instead of setting.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: project-15.0/project-15.0-project_forecast_line
Translate-URL: https://translation.odoo-community.org/projects/project-15-0/project-15-0-project_forecast_line/
Add computed fields to written fields to trigger forecast lines update
Add hook for several UoM hours/days conversion
gurneyalex and others added 25 commits March 6, 2024 10:20
Fix an issue in project_forecast_line where lines would be removed by
the cron.

When an employee has a forecast role with an end date set, depending on
the order of the processing of records in the cron, a bug could remove
forecast lines of other employees when attempting to remove the forecast
lines related to thatrole which had been generated after the end date in
previous runs (before the end date was set).

Fix this by using the correct domain.
Currently translated at 100.0% (95 of 95 strings)

Translation: project-15.0/project-15.0-project_forecast_line
Translate-URL: https://translation.odoo-community.org/projects/project-15-0/project-15-0-project_forecast_line/it/
Currently translated at 100.0% (95 of 95 strings)

Translation: project-15.0/project-15.0-project_forecast_line
Translate-URL: https://translation.odoo-community.org/projects/project-15-0/project-15-0-project_forecast_line/it/
Currently translated at 100.0% (95 of 95 strings)

Translation: project-15.0/project-15.0-project_forecast_line
Translate-URL: https://translation.odoo-community.org/projects/project-15-0/project-15-0-project_forecast_line/it/
Currently translated at 100.0% (95 of 95 strings)

Translation: project-15.0/project-15.0-project_forecast_line
Translate-URL: https://translation.odoo-community.org/projects/project-15-0/project-15-0-project_forecast_line/it/
when running in multi company, sometimes the user making a change is not connected
using the company of the record. In this case the default value for company_id on
forecast.line will lead to a wrong forecast.

we fix this by using the best company when updating the forecast (the
employee's company for task assigned to employees or leaves, the sale
line's company for sales forecast
the condition was wrong, preventing the fast update from being used
when only the remaining time is updated
Currently translated at 100.0% (95 of 95 strings)

Translation: project-15.0/project-15.0-project_forecast_line
Translate-URL: https://translation.odoo-community.org/projects/project-15-0/project-15-0-project_forecast_line/it/
when using the quick update, we would get an inversion of the sign of the forecast
because the ratio was negative
Currently translated at 100.0% (95 of 95 strings)

Translation: project-15.0/project-15.0-project_forecast_line
Translate-URL: https://translation.odoo-community.org/projects/project-15-0/project-15-0-project_forecast_line/es/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: project-15.0/project-15.0-project_forecast_line
Translate-URL: https://translation.odoo-community.org/projects/project-15-0/project-15-0-project_forecast_line/
Currently translated at 100.0% (95 of 95 strings)

Translation: project-15.0/project-15.0-project_forecast_line
Translate-URL: https://translation.odoo-community.org/projects/project-15-0/project-15-0-project_forecast_line/it/
Currently translated at 100.0% (95 of 95 strings)

Translation: project-15.0/project-15.0-project_forecast_line
Translate-URL: https://translation.odoo-community.org/projects/project-15-0/project-15-0-project_forecast_line/it/
@thomaspaulb
Copy link
Member

@ntsirintanis Should I merge this in? It will probably make your PR red

@ntsirintanis ntsirintanis force-pushed the 16.0-mig-project_forecast_line branch from a5080b7 to 60e358f Compare October 24, 2024 07:04
@ntsirintanis
Copy link

@QuiJoQuim thanks for this MR! Please rebase, let's see if we can make this green

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

Successfully merging this pull request may close these issues.