-
Notifications
You must be signed in to change notification settings - Fork 8.3k
feat: add routing/sequencing to work order operations #46975
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
Merged
Merged
Conversation
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
This pull request has been automatically marked as inactive because it has not had recent activity. It will be closed within 3 days if no further activity occurs, but it only takes a comment to keep a contribution alive :) Also, even if it is closed, you can always reopen the PR when you're ready. Thank you for contributing. |
mergify bot
pushed a commit
that referenced
this pull request
May 13, 2025
* feat: add routing/sequencing to work order operations * fix: add validation and remove reorderin for non sequence id operations * chore: readability * fix: logical error * fix: logical error * chore: added row number in error message (cherry picked from commit f1159b6) # Conflicts: # erpnext/manufacturing/doctype/work_order_operation/work_order_operation.json
rohitwaghchaure
pushed a commit
that referenced
this pull request
May 13, 2025
… (#47534) * feat: add routing/sequencing to work order operations (#46975) * feat: add routing/sequencing to work order operations * fix: add validation and remove reorderin for non sequence id operations * chore: readability * fix: logical error * fix: logical error * chore: added row number in error message (cherry picked from commit f1159b6) # Conflicts: # erpnext/manufacturing/doctype/work_order_operation/work_order_operation.json * chore: resolve conflicts --------- Co-authored-by: Mihir Kandoi <kandoimihir@gmail.com>
frappe-pr-bot
pushed a commit
that referenced
this pull request
May 13, 2025
# [15.61.0](v15.60.2...v15.61.0) (2025-05-13) ### Bug Fixes * accumulate values for all the fiscal years in Profit And Loss Statement ([6dbdc36](6dbdc36)) * added PR/PI overbilling validation (backport [#47385](#47385)) ([#47497](#47497)) ([309ea7b](309ea7b)) * broken test suite due to incorrect OR filter ([4a37f2a](4a37f2a)) * condition for advance_account assignment ([b6e5e33](b6e5e33)) * do not mandate depreciation accounts for non depreciable asset category ([a75931c](a75931c)) * dont auto-fetch latest exchange rate ([0adb715](0adb715)) * error while making SABB for backdated stock reco ([7ba7d1a](7ba7d1a)) * ignore "Account Closing Balance" doctype on Period Closing Voucher cancellation ([39c0291](39c0291)) * only depreciable category assets are allowed for depreciation ([242a119](242a119)) * **payment-reconciliation:** use reconciliation_takes_effect_on from company ([25fabda](25fabda)) * POS non-stock item mistakenly hidden as unavailable (backport [#47493](#47493)) ([#47506](#47506)) ([b18692c](b18692c)) * resolved conflicts ([dcfae61](dcfae61)) * timesheet portal showing total billing hours ([64ae4e1](64ae4e1)) * typo ([d61a85e](d61a85e)) * typo in event.js ([67d24e9](67d24e9)) * warning message for COGS account in the stock entry ([7abe199](7abe199)) ### Features * add non depreciable category checkbox in asset category ([96d3bfd](96d3bfd)) * add routing/sequencing to work order operations (backport [#46975](#46975)) ([#47534](#47534)) ([56d0357](56d0357)) ### Performance Improvements * Skip link checking on repost's remove_attached_file (backport [#45061](#45061)) ([#47450](#47450)) ([09e7bfb](09e7bfb))
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.
Reference support ticket 34982
no-docs
Note: linter error is a warning, everything is working as expected.