Repository navigation
stock_available_to_promise: un-release moves becoming no more available to promise #1079
Description
Is your feature request related to a problem?
In some cases, the conditions for releasing outgoing moves already released are no longer met. In such cases, we end up with waiting operations in related picking processes that are no longer possible.
Describe the solution you'd like
The idea it to track the change of state of operations of specific picking types that are generated from the release of moves. In the event of a change of status or confirmation, if it becomes unavailable, we could check on the original movement whether it is still releasable and, if not, un-release it
- The original move will be provided by the stock_move_propagate_first_move addon
- In place of checking on the change of status, we could base our trigger on the one from the stock_move_auto_assign addon
Additional context
The proposed approach is a technical shortcut to try to put in place an efficient solution to the need to find a way to un-release outgoing moves that are no more available to promise.
Activity
lmignon commentedon Jul 7, 2025
@jbaudoux WDYT?
github-actions commentedon Jan 4, 2026
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 commentedon Aug 16, 2026
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.