-
Notifications
You must be signed in to change notification settings - Fork 66
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
Ensures all pending items are addressed before marking the cycle count as complete #635
Labels
Comments
R-Sourabh
added a commit
to R-Sourabh/inventory-count
that referenced
this issue
Jan 17, 2025
…hen no items are in the "created" state(hotwax#635)
R-Sourabh
added a commit
to R-Sourabh/inventory-count
that referenced
this issue
Jan 17, 2025
1 task
R-Sourabh
added a commit
to R-Sourabh/inventory-count
that referenced
this issue
Jan 17, 2025
…count in a cycle count(hotwax#635)
R-Sourabh
added a commit
to R-Sourabh/inventory-count
that referenced
this issue
Jan 17, 2025
ravilodhi
added a commit
that referenced
this issue
Jan 17, 2025
Improved: Added a check to allow completing the pending count only when no items are in the "created" state(#635)
R-Sourabh
added a commit
to R-Sourabh/inventory-count
that referenced
this issue
Jan 17, 2025
…s the pending count(hotwax#635)
Merged
1 task
R-Sourabh
added a commit
to R-Sourabh/inventory-count
that referenced
this issue
Jan 17, 2025
ymaheshwari1
added a commit
that referenced
this issue
Jan 17, 2025
Improved: Added a loader in the complete count function that completes the pending count(#635)
Issue verified and working fine in release v2.6.1. Hence, closing this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current behavior
Currently the checks are there at app side to handle this but somehow user completed the Cycle count without addressing pending review items.
Expected behavior
Check in DB for any open item in the Cycle count before marking it as completed.
Steps to reproduce the issue
Can you handle fixing this bug by yourself?
Environment details
Additional information
The text was updated successfully, but these errors were encountered: