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
Expected Behavior (or desired behavior if a feature request)
When I check out a consumable, the consumable has been used up, it's never going to be checked back in. The starting quantity should be decremented.
Actual Behavior
Checking out a consumable leaves the original quantity unaltered. For example, if I start with 10 reams of paper, and 10 are checked out so I purchase another 5, I now have to adjust the quantity in SnipeIT to 15 so that my remaining quantity shows '5' This seems like acceptable behavior for assets which could b returned and checked back in, but not for consumables which are used up and never coming back.
This is on SnipeIT version 5.1.1, if there's a better way of accomplishing what I need I'm more then happy to entertain altering my workflow.
The text was updated successfully, but these errors were encountered:
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
Expected Behavior (or desired behavior if a feature request)
When I check out a consumable, the consumable has been used up, it's never going to be checked back in. The starting quantity should be decremented.
Actual Behavior
Checking out a consumable leaves the original quantity unaltered. For example, if I start with 10 reams of paper, and 10 are checked out so I purchase another 5, I now have to adjust the quantity in SnipeIT to 15 so that my remaining quantity shows '5' This seems like acceptable behavior for assets which could b returned and checked back in, but not for consumables which are used up and never coming back.
This is on SnipeIT version 5.1.1, if there's a better way of accomplishing what I need I'm more then happy to entertain altering my workflow.
The text was updated successfully, but these errors were encountered: