We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If a component stock is down to one item, it's not possible to checkout this last one to an asset.
I can checkout components down to the very last one, so none is available anymore after the checkout (stock = 0).
v6.1.0
Official Docker Image (Ubuntu 20.04.6)
Official Docker Image (Apache2 2.4.41)
Official Docker Image (7.4.3)
No response
I think I already found the culprit and will post a PR trying to fix this issue.
The text was updated successfully, but these errors were encountered:
Allow checkout of available components down to zero stock (fixes snip…
0c16d97
…e#12854)
Fixed snipe#12854: Allow checkout of available components down to zer…
04f3c4b
…o stock
Merge pull request #12855 from koelle25/fixes/last_component_checkout
b22cad9
Allow checkout of available components down to zero stock (fixes #12854)
Successfully merging a pull request may close this issue.
Debug mode
Describe the bug
If a component stock is down to one item, it's not possible to checkout this last one to an asset.
Reproduction steps
Expected behavior
I can checkout components down to the very last one, so none is available anymore after the checkout (stock = 0).
Screenshots
Snipe-IT Version
v6.1.0
Operating System
Official Docker Image (Ubuntu 20.04.6)
Web Server
Official Docker Image (Apache2 2.4.41)
PHP Version
Official Docker Image (7.4.3)
Operating System
No response
Browser
No response
Version
No response
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
No response
Additional context
I think I already found the culprit and will post a PR trying to fix this issue.
The text was updated successfully, but these errors were encountered: