You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I am working on an inbound shipment that has been automatically generated (from an outbound shipment in another store), I can not:
Set a line to have a quantity of 0
Add a line and then delete it
The option is disabled.
I can see why this would happen since we don't want too much editing of lines that came from another store but...what if I really didn't receive anything? I shouldn't have to return stock I didn't receive in the first place.
Expected behaviour 🤔
Two fields? One that shows what I was sent, and one that shows what I received. I should be able to set the received field to zero
And...if I added the line myself (ie. sent = 0) then I should be able to delete it.
How to Reproduce 🔨
Steps to reproduce the behaviour:
Create an outbound shipment in Store A (to Store B)
open the inbound shipment created in store B
Add a line, try to delete. OR try to set the qty of a line to 0
See error
Your environment 🌱
Open mSupply Version: 2.5.0
Platform: demo-oms
The text was updated successfully, but these errors were encountered:
What went wrong? 😲
If I am working on an inbound shipment that has been automatically generated (from an outbound shipment in another store), I can not:
The option is disabled.
I can see why this would happen since we don't want too much editing of lines that came from another store but...what if I really didn't receive anything? I shouldn't have to return stock I didn't receive in the first place.
Expected behaviour 🤔
Two fields? One that shows what I was sent, and one that shows what I received. I should be able to set the received field to zero
And...if I added the line myself (ie. sent = 0) then I should be able to delete it.
How to Reproduce 🔨
Steps to reproduce the behaviour:
Your environment 🌱
The text was updated successfully, but these errors were encountered: