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

[14.0][IMP] stock_quant_manual_assign: Add an option to allow hijacking serial numbers #2100

Draft
wants to merge 1 commit into
base: 14.0
Choose a base branch
from

Conversation

thomaspaulb
Copy link

When this option is set on the corresponding stock picking type, it's possible to select a serial number even though it's already reserved in another place. It will be unreserved there, and assigned to where you currently are.

SITUATION: A can't select serial number because it's already reserved by B

image

AFTER: A selected serial number, and got unreserved at B

image

@thomaspaulb thomaspaulb changed the title [IMP] stock_quant_manual_assign: Add an option to allow hijacking serial numbers [14.0][IMP] stock_quant_manual_assign: Add an option to allow hijacking serial numbers Jul 8, 2024
@thomaspaulb thomaspaulb force-pushed the 14.0-stock_quant_manual_assign-hijack_other branch from 81af1d4 to bc15ca7 Compare July 8, 2024 19:43
@thomaspaulb thomaspaulb marked this pull request as draft July 8, 2024 21:11
@thomaspaulb thomaspaulb force-pushed the 14.0-stock_quant_manual_assign-hijack_other branch from bc15ca7 to 1702408 Compare July 9, 2024 09:09
…ial numbers

When this option is set on the corresponding stock picking type, it's possible to
select a serial number even though it's already reserved in another place. It will
be unreserved there, and assigned to where you currently are.
@thomaspaulb thomaspaulb force-pushed the 14.0-stock_quant_manual_assign-hijack_other branch from 1702408 to 9af2728 Compare July 9, 2024 09:15
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 Nov 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant