Skip to content

Conversation

@rousseldenis
Copy link
Contributor

@rousseldenis rousseldenis commented Oct 6, 2023

@rousseldenis rousseldenis force-pushed the 16.0-add-stock-picking-operation-loss-dro branch 2 times, most recently from 368c3d7 to dff9c13 Compare October 9, 2023 08:48
@rousseldenis rousseldenis marked this pull request as ready for review October 17, 2023 07:28
@rousseldenis rousseldenis added this to the 16.0 milestone Oct 17, 2023
@lmignon
Copy link
Contributor

lmignon commented Dec 20, 2023

depends on #1330

@lmignon lmignon force-pushed the 16.0-add-stock-picking-operation-loss-dro branch from 255be27 to bf41a93 Compare December 21, 2023 08:01
@rousseldenis
Copy link
Contributor Author

What this module needs is to make the user access inventory easily through the Loss picking menu

@rousseldenis rousseldenis force-pushed the 16.0-add-stock-picking-operation-loss-dro branch from 3bd8305 to 56858c3 Compare April 2, 2024 09:31
@github-actions
Copy link

github-actions bot commented Aug 4, 2024

There hasn't been any activity on this pull request in the past 4 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 PR 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 Aug 4, 2024
rousseldenis and others added 5 commits September 3, 2024 10:08
…on inventory

 When an inventory is validated, we need to cancel any remaining pending moves created to make the quantity no more available in case of loss declaration.
…ancel the loss move

When user want to apply inventory, be less restrictive on inventory_mode
check as the values should have been checked in stock module.
@rousseldenis rousseldenis force-pushed the 16.0-add-stock-picking-operation-loss-dro branch from 56858c3 to 8b3802c Compare September 3, 2024 08:13
@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Sep 8, 2024
@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 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 PR 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 Jan 12, 2025
@github-actions github-actions bot closed this Feb 16, 2025
@lmignon
Copy link
Contributor

lmignon commented Aug 19, 2025

ping @rousseldenis This one is used in our project and in production for years...

@rousseldenis rousseldenis reopened this Aug 20, 2025
@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants