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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set Quantities to 0 in Inbound Shipment doesn't work and shows incorrect error #4357

Open
roxy-dao opened this issue Jul 3, 2024 · 0 comments 路 May be fixed by #4366
Open

Set Quantities to 0 in Inbound Shipment doesn't work and shows incorrect error #4357

roxy-dao opened this issue Jul 3, 2024 · 0 comments 路 May be fixed by #4366
Assignees
Labels
bug Something is borken Severity: High Bugs breaking core functionality or with no/unacceptable workaround. High impact. Next patch release Team Ruru 馃 Lach茅, Carl, Andrei
Milestone

Comments

@roxy-dao
Copy link
Contributor

roxy-dao commented Jul 3, 2024

What went wrong? 馃槻

When navigating to Replenishment -> Inbound Shipment, you can select a line in a new Inbound Shipment. Once an item is selected, you can then click Actions -> Set Quantities to 0 and that's when 2 incorrect errors pop up. The item I was using had quantity > 0 and the status of the Inbound Shipment was New.

Expected behaviour 馃

If the requirements are satisfied (e.g. the Inbound Shipment is New and quantity > 0), then you should be able to perform the function and set quantities to 0.

How to Reproduce 馃敤

Steps to reproduce the behaviour:

  1. Go to Replenishment -> Inbound Shipment
  2. Create a new Inbound Shipment and add an item to it
  3. Select that item, go to Actions -> Set Quantity to 0
  4. See 2 errors pop up

Your environment 馃尡

  • Open mSupply Version: V2.1.0-RC4
  • Legacy mSupply Central Server Version: V7.15.05
  • Platform: Desktop app on Windows and Galaxy Tab A8 Android App
  • Database type: SQLite3
@roxy-dao roxy-dao added bug Something is borken needs triage needs daily triage New bug to be triaged by the release team labels Jul 3, 2024
@andreievg andreievg added this to the V2.2.0 milestone Jul 3, 2024
@mark-prins mark-prins added Team Ruru 馃 Lach茅, Carl, Andrei and removed needs triage needs daily triage New bug to be triaged by the release team labels Jul 3, 2024
@andreievg andreievg added needs triage needs daily triage New bug to be triaged by the release team labels Jul 3, 2024
@andreievg andreievg added Severity: High Bugs breaking core functionality or with no/unacceptable workaround. High impact. Next patch release and removed needs triage needs daily triage New bug to be triaged by the release team labels Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is borken Severity: High Bugs breaking core functionality or with no/unacceptable workaround. High impact. Next patch release Team Ruru 馃 Lach茅, Carl, Andrei
Projects
None yet
3 participants