[IMP] Manufacturing: Resolving work order dependency problems#17301
Open
erjer-odoo wants to merge 1 commit into18.0from
Open
[IMP] Manufacturing: Resolving work order dependency problems#17301erjer-odoo wants to merge 1 commit into18.0from
erjer-odoo wants to merge 1 commit into18.0from
Conversation
Collaborator
|
|
Contributor
Author
|
Hi @meval1006 -- this PR is ready for review when you have a moment. Thank you! |
meval1006
approved these changes
Apr 9, 2026
Contributor
meval1006
left a comment
meval1006
left a comment
There was a problem hiding this comment.
Hi Erin, I had a few style corrections and some suggestions. The biggest one is to retake the images of the Work Order tab so that all the column titles are fully visible, giving the reader better context in the images. It's a hassle, so I will leave the final decision to you. After the style changes, you should be good to go.
| Problems are indicated by the red :icon:`fa-exclamation-triangle` :guilabel:`(exclamation triangle)` | ||
| icon on the work order line. | ||
|
|
||
| .. image:: work_order_dependencies/mo-scheduling-problem.png |
Contributor
There was a problem hiding this comment.
Suggestion: I know it would be a hassle, but I recommend retaking screenshots that include the columns and ensuring the column titles are fully visible. This ensures there is enough context for the reader.
| begin. In order to ensure operations are carried out in the correct order, Odoo *Manufacturing* | ||
| features a *work order dependencies* setting. Enabling this setting allows for operations on a Bill | ||
| of Materials (BoM) to be *blocked* by other operations that should occur first. | ||
| begin. To ensure operations are carried out in the correct order, the *Manufacturing* app features a |
Contributor
There was a problem hiding this comment.
Suggested change
| begin. To ensure operations are carried out in the correct order, the *Manufacturing* app features a | |
| begin. To ensure operations are carried out in the correct order, the **Manufacturing** app features a |
Correction: App names should be bold.
...lications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst
Show resolved
Hide resolved
| After confirming the manufacturing order, select the :guilabel:`Work Orders` tab to view the work | ||
| orders required to complete it. Any work orders that are *not* blocked by a different work order | ||
| display a `Ready` tag in the :guilabel:`Status` section. | ||
| After confirming the manufacturing order, open the *Work Orders* tab to view the work orders |
Contributor
There was a problem hiding this comment.
Suggested change
| After confirming the manufacturing order, open the *Work Orders* tab to view the work orders | |
| After confirming the manufacturing order, open the :guilabel:`Work Orders` tab to view the work orders |
Correction: If the tab is part of the instruction action, then it should be a guilabel.
...lications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst
Show resolved
Hide resolved
Comment on lines
+9
to
+10
| *work order dependencies* setting. Enabling this setting allows for operations on a Bill of | ||
| Materials (BoM) to be *blocked* by other operations that should occur first. |
Contributor
There was a problem hiding this comment.
Suggested change
| *work order dependencies* setting. Enabling this setting allows for operations on a Bill of | |
| Materials (BoM) to be *blocked* by other operations that should occur first. | |
| *work order dependencies* setting. Enabling this setting blocks the Bill of | |
| Materials (BoM) operations when other operations should occur first. |
Suggestion: revise to make it direct and concise.
Comment on lines
+60
to
+61
| After work order dependencies are configured for a |BOM|, the *Manufacturing* app can plan when work | ||
| orders are scheduled based on those dependencies. To plan the work orders for a manufacturing order, |
Contributor
There was a problem hiding this comment.
Suggested change
| After work order dependencies are configured for a |BOM|, the *Manufacturing* app can plan when work | |
| orders are scheduled based on those dependencies. To plan the work orders for a manufacturing order, | |
| After work order dependencies are configured for a |BOM|, the *Manufacturing* app can plan work | |
| order schedules based on those dependencies. To plan the work orders for a manufacturing order, |
Suggestion: shortened the sentence.
Comment on lines
+103
to
+104
| If a work order is blocked by the completion of another, the blocked work order is shown as | ||
| scheduled to start after the work order that blocks it. In addition, an arrow connects the two work |
Contributor
There was a problem hiding this comment.
Suggested change
| If a work order is blocked by the completion of another, the blocked work order is shown as | |
| scheduled to start after the work order that blocks it. In addition, an arrow connects the two work | |
| If a work order is blocked by another, the blocked work order is shown as | |
| scheduled to start after the blocking work order. In addition, an arrow connects the two work |
Suggestion: Revision to make this sentence less wordy and improve clarity.
...lications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst
Show resolved
Hide resolved
|
|
||
| Click the red :icon:`fa-exclamation-triangle` :guilabel:`(exclamation triangle)` icon, then click | ||
| :guilabel:`Replan` in the *Scheduling Information* pop-up window. The work order is rescheduled to | ||
| maintain the work order dependencies. |
Contributor
There was a problem hiding this comment.
Suggested change
| maintain the work order dependencies. | |
| maintain its dependencies. |
Suggestion
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Task card.
In addition to the requests in the task card, I have updated the documentation for how work order dependencies function in 18.0 and aligned the screenshots with our current guidelines.
This 18.0 PR should not be FWP. There are changes in 19 that warrant their own PR.