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][migrate][mrp_production_date_planned_finished] Improve Manufacturing Order Duration Management in Odoo 16 #1112

Closed
nagybal opened this issue Oct 17, 2023 · 2 comments
Labels
enhancement stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@nagybal
Copy link

nagybal commented Oct 17, 2023

Is your feature request related to a problem?
Yes, in Odoo 16, the planned duration of Manufacturing Orders (MO) can't be altered directly. While users can display and adjust the planned finish date, Odoo doesn't maintain the set duration when the MO is rescheduled. This results in the system defaulting to the Manufacturing Lead Time from the product template.

Issues Identified:
The new duration of the MO gets overridden, causing loss of user-defined durations.

  1. Dragging MO in the calendar view changes the start date but doesn't keep the intended duration.
  2. Using the hamburger-menu to adjust the finish date doesn't maintain the new duration. Screenshot 2023-10-17 at 23 02 24

Testing
The issue has been verified on runboat.

Describe the solution you'd like
Your add-on, mrp_production_date_planned_finished, resolves this problem. Please consider migrating it to support Odoo 16.

Describe alternatives you've considered

  1. Make the date_planned_finished field visible by default in the MO form view.
  2. Identify and remove the Python code that's resetting the MO duration to the manufacturing lead time.

Additional context
The current behavior is problematic as it disregards user-set durations for specific MOs, negating manual calculations made for production timings.

@nagybal
Copy link
Author

nagybal commented Oct 17, 2023

@ivantodorovich could You please take a look?

Copy link

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Apr 21, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

1 participant