Issue title: Checkout Consumables Totals
 Issue body: #### Expected Behavior (or desired behavior if a feature request)

checkout consumables 5 pens, 3 reams of paper, 15 boxes of clips to 1 person or 1 location or machine

-----

#### Actual Behavior

instead of checking out 5 pens, i have to check out 1 pen 5 times and 1 ream on papers 3 times and 1 box 15 times to the same person, VERY EXHAUSTING... Please help!!!

-----

#### Please confirm you have done the following before posting your bug report:

- [Yes] I have enabled debug mode 
- [Yes] I have read [checked the Common Issues page](https://snipe-it.readme.io/docs/common-issues)

-----
#### Provide answers to these questions:

- Is this a fresh install or an upgrade?  - Yes
- Version of Snipe-IT you're running - v4.1.14 build 3382 (g0f23462)
- Version of PHP you're running
- Version of MySQL/MariaDB you're running
- What OS and web server you're running Snipe-IT on
- What method you used to install Snipe-IT (install.sh, manual installation, docker, etc)
- WITH DEBUG TURNED ON, if you're getting an error in your browser, include that error
- What specific Snipe-IT page you're on, and what specific element you're interacting with to trigger the error
- If a stacktrace is provided in the error, include that too.
- Any errors that appear in your browser's error console.
- Confirm whether the error is reproducible on the demo: https://snipeitapp.com/demo.
- Include any additional information you can find in `storage/logs` and your webserver's logs.
- Include what you've done so far in the installation, and if you got any error messages along the way.
- Indicate whether or not you've manually edited any data directly in the database

Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you.

https://snipe-it.readme.io/docs/getting-help

 Comments: 
 Comment 0: I agree with this. 
 Comment 1: Apologies for opening this or commenting on this issue. However, i would like to request if any solution was found for this issue as I would like to have the same implemented. @snipe @chaaza 
 Comment 2: This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

 Comment 3: Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

 Comment 4: +1
 Comment 5: This. Please. :)
 Comment 6: Please add this features.
 Comment 7: nned the bulk Checkout Consumables, pls :D
 Comment 8: I need this feature, please. I am trying to keep up with business audits.
 Comment 9:       Hi @snipe @chaaza please help us out on this issue as we are having a very difficult time with checking out these consumables and accessories. For eg if I were to check out 24 RJ45 connectors I had to check the same out 24 time. I see that under your component checkout module, you have included the quantity field and there you are easily able to add the quantity.
     Also a reason field for the checkout of consumables need to be displayed, so that when a report is generated you have a solid reason for checking out these consumables. It's a humble request that you help us out in this regard.  I'm a university's IT store manager and  we came across your asset management S/W and immediately deployed it on our hosted servers.
     I understand that since this is an open source S/W you need time to have these incorporated but this feature will make life easy for so many of us here. I'm pretty sure of it. You can also send me a reply personally on my GITHUB. Looking forward to hear from you.
![comsumable](https://user-images.githubusercontent.com/45507622/49326159-e3a87880-f55e-11e8-96cd-fcdd7f072d0b.PNG)

 Comment 10: Another vote for this, would be really handy
 Comment 11: Please help me out here @snipe @chaaza 
 Comment 12: @hatimdegani it’s in the roadmap, but we haven’t had a chance to work on it yet.
 Comment 13: Thank for replying 
 Comment 14: Any ETA or a work around will be really appreciated as, we are building up our inventory and at times checking out so many consumables is a hassle. The check out by quantity feature is available in components module, so why not make it available on consumables and accessories too. I'm sure there must be a very good reason why but this makes snipe IT only good for recording assets and not fully use its potential.
 Comment 15: +1, this can also fit for stuff like patchcords for networking teams - totally must have!
 Comment 16: +1 vote for me as well.
 Comment 17: hey guys I would like to add my voice to the masses begging for this feature.  I too have to check out multiple mbell@example.com.  Thank you for adding this to the feature request list.
 Comment 18: ... this is a critical feature for me: I was considering Snipe-IT for my lab, but now I'm totally bummed out by the inexplicable omission of this feature. No action or even substantive comments for a year (since #5173 was opened)... If there was an ETA at least, I'd probably still go ahead with trying Snipe-IT out. 
 Comment 19: > now I'm totally bummed out by the inexplicable omission of this feature.

Sorry to bum you out. It's not "inexplicable". There are hundreds of feature requests that come through every week. We address a lot of them, but we're a small team, and changing this changes the way we currently handle those models in significant ways. 

> No action or even substantive comments for a year (since #5173 was opened)

We've pushed [580+ commits to master](https://github.com/snipe/snipe-it/compare/v4.2.0...master), with even more on develop, (and released a dozen times) since that feature request was opened. While I realize that doesn't address this specific feature, the point is that a lot of work gets done on this project all the time. Sometimes it happens that the feature you need doesn't get worked on as quickly as you'd like, while we work on features that are just as important to other folks. 

If it's that important to you, we'd certainly welcome a pull request. Otherwise, we appreciate your patience. 

 Comment 20: … fair enough. It is understood that there are many reasonable 
features, and prioritization is required.

"Inexplicable" in this case referred to my opinion of the design 
decision: just coding for decrementing by one instead of right away 
addressing multiples of one in the situation where the generalization is 
clearly likely to be useful. To me this indicates a certain philosophy 
and suggests numerous other cases of arbitrary limitations in the 
system. I hope I am incorrect in this expectation.

Do you have a bounty system for implementing feature requests? It will 
be more efficient if somebody familiar with the codebase implemented 
this request, and with a reasonable bounty (which I would pay) perhaps a 
3rd party contributor could write a patch in half an hour.



On 18 Apr 2019, at 14:35, snipe wrote:

> > now I'm totally bummed out by the inexplicable omission of this 
> feature.
>
> Sorry to bum you out. It's not "inexplicable". There are hundreds of 
> feature requests that come through every week. We address a lot of 
> them, but we're a small team, and changing this changes the way we 
> currently handle those models in significant ways.
>
>> No action or even substantive comments for a year (since #5173 was 
>> opened)
>
> We've pushed [580+ commits to 
> master](https://github.com/snipe/snipe-it/compare/v4.2.0...master), 
> with even more on develop, (and released a dozen times) since that 
> feature request was opened. While I realize that doesn't address this 
> specific feature, the point is that a lot of work gets done on this 
> project all the time. Sometimes it happens that the feature you need 
> doesn't get worked on as quickly as you'd like, while we work on 
> features that are just as important to other folks.
>
> If it's that important to you, we'd certainly welcome a pull request. 
> Otherwise, we appreciate your patience.
>
>
> -- 
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> https://github.com/snipe/snipe-it/issues/5176#issuecomment-484631799



 Comment 21: Was hoping to use Consumables as a means of tracking feet/metres of cable. 
But without bulk checkout, it's completely infeasible to consume hundreds of feet of cable per project ... foot-by-foot ... 

Is there an alternative way of using the software in the meantime, until bulk checkout of consumables is coded in, for the above intended use ?
 Comment 22: I also miss this feature a lot. Bulk checkout would make handling of consumables so much easier. Please consider to add this. Thank you.
 Comment 23: bump.
> 
> 
> @hatimdegani it’s in the roadmap, but we haven’t had a chance to work on it yet.

Thank you! 
 Comment 24: > 
> 
> Was hoping to use Consumables as a means of tracking feet/metres of cable.
> But without bulk checkout, it's completely infeasible to consume hundreds of feet of cable per project ... foot-by-foot ...
> 
> Is there an alternative way of using the software in the meantime, until bulk checkout of consumables is coded in, for the above intended use ?

I'll love to hear if anyone has come with workarrounds using other software or even into snipeit. 

I was thinking on using the components section since it lets you bulk check out  but it only lets you check out for device :(.


 Comment 25: Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

 Comment 26: i still need this feature or workaround to checkout quantity more than 1
 Comment 27: Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

 Comment 28: This is still very relevant to our company yes.  If you guys could work it into your roadmap we would be very happy.

From: stale[bot] <mbell@example.com>
Sent: Tuesday, August 27, 2019 1:27 PM
To: snipe/snipe-it <mbell@example.com>
Cc: Michael J. Sweeney <mbell@example.com>; Comment <mbell@example.com>
Subject: Re: [snipe/snipe-it] Checkout Consumables Totals (#5176)


Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/snipe/snipe-it/issues/5176?email_source=notifications&email_token=AKWGDUQAKVHPLOCKUOATTTTQGVWX3A5CNFSM4EUPRAFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5IVZBI#issuecomment-525425797>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AKWGDUWV2APGQCYGDVVX7C3QGVWX3ANCNFSM4EUPRAFA>.

Michael Sweeney
IT Manager
3941 Harry S Truman Blvd
St Charles, MO 63301
Office:  907.813.5593
Fax:  907.813.5593
Email: mbell@example.com <mailto:%mbell@example.com>
[EPC]
EPC, Inc. - Established in 1984
A wholly owned subsidiary of CSI Leasing, Inc.

www.epcusa.com<http://www.epcusa.com/>
Read our whitepaper IT Security Risks: Overlooked Vulnerabilities & Best Practices!<http://epcusa.hs-sites.com/it-security-risks-overlooked-vulnerabilities-best-practices-white-paper>

[Follow us on Facebook]<http://epcgo.to/facebook> [Follow us on LinkedIn] <http://epcgo.to/linkedin>  [Follow us on Twitter] <http://epcgo.to/twitter>

 Comment 29: Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

 Comment 30: +1 for this feature, I would add that we should be able to put a default qty to check out in the setup
 Comment 31: Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

 Comment 32: +2, can't deploy snipe it until this feature is added, as there is no other workaround 
 Comment 33: +1 for this feature, I would make a huge positive difference in our workflow
 Comment 34: 
Can i code it admin?
 Comment 35: I start using snipe from Oct 2018. It's very nice tool for it asset managemnet.
 Comment 36: > Can i code it admin?

Please do, snipe doesn't mind pull requests.. if you can do it, you'll do us all a huge favor, right @snipe ?
 Comment 37: Bought snipe-it hosted licence yesterday to track assets, licences & consumables.

Person in charge of consumables just told me they will stick to their Excel spreadsheet rather than check out every consumable item 1 by 1 so we just can't use the whole consumable side of this product until our user can type "24" then "submit" instead of having to press the checkout button 24 times!
 Comment 38: Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

 Comment 39: Yes, we still cannot deploy until this is enabled

On Jan 20, 2020 10:33 AM, "stale[bot]" <mbell@example.com> wrote:

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/snipe/snipe-it/issues/5176?email_source=notifications&email_token=AGBSOSZWTNZ6BPOSUIWJVJLQ6UEQHA5CNFSM4EUPRAFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJLFEBQ#issuecomment-576082438>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGBSOS4S6IY2PCQ4OEUURX3Q6UEQHANCNFSM4EUPRAFA>.


 Comment 40: Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

 Comment 41: Any idea, whether an implementation is possible this year? Thx!
 Comment 42: Would love to know if this has any sort of ETA, this really limits the use case for us. 

A standard install will take multiple consumables, checking out 75 patch leads individually just isn't going to happen.
 Comment 43: would love to see this feature coming as well :)
 Comment 44: Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

 Comment 45: It is still relevant
 Comment 46: Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

 Comment 47: Not relevant for me anymore, I opted for another software because of it.
Am 25. Apr. 2020, 14:36 +0200 schrieb stale[bot] <mbell@example.com>:
> Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub, or unsubscribe.

 Comment 48: > Not relevant for me anymore, I opted for another software because of it. Am 25. Apr. 2020, 14:36 +0200 schrieb stale[bot] <mbell@example.com>:
> […](#)
> Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

Which software did you opt to?
 Comment 49: I have been paying $40 a month for a hosted instance for about 6 months now, hoping for it to be fixed. But I am also looking for something else now as I see these sort of things getting closed automatically then opened automatically when people say it is needed but I can't see fixes.
 Comment 50: Well, we ended up changing our entire software infrastructure on the debtor and creditor side incl warehouse management. Using a combination of Weclapp and Shopware with (Add-ons and Plug-ins) now. Sorry, these are of course not really comparable with this compact solution.

 


 Comment 51: Just came to use this product; ideally, I would want users to be able to adjust how many consumables are left - they are not always checked out as such. Secondly, users should be able to check out multiple of a unit at any one time.
 Comment 52: Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

 Comment 53: +1
 Comment 54: Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

 Comment 55: When will this be developed/implemented? Is there a timeline?
 Comment 56: > When will this be developed/implemented? Is there a timeline?

yes I'd like to see this implemented ASAP @snipe 
 Comment 57: We're implementing Snipe-IT and a possibility to checkout multiple consumables is important in our stock flows.
As this thread is aged 2,5 year, I'm looking forward :) 
 Comment 58: Some of my students are at loose ends at the moment. 
I would like to task them with possibly adding this module.
May we help?

So...

Query
What should the workflow look like to check out 1-? items? 

Pop up?
Field input?
Add a variable quantity field to /consumables/311/checkout   ?

T


 Comment 59: Hi Tsilman,


Many thanks for reaching out!


The last one fits my requitements best.


I would like to be able to checkout several same consumables to one user/location/asset with one operation.


Example:


Consumable 0.5m cat5e patchcord quantity 100


Checkout to user/location/asset 27 such patchcords.


Right now I need to conduct 27 checkout operations.


Ideally I wolud like to conduct 1 checkout operation with field quantity set to 27.


Ressuming, in the first place adding field quantity to checkout screen for consumables wolud be great. Ideally it could be just a copy of checkout screen that already exists for components :)




Have a nice day,


PiChG




Wysłano z mojego smartfonu w Play


Get Outlook for Android







On Tue, Aug 25, 2020 at 6:02 PM +0200, "tsilman-marquette" <mbell@example.com> wrote:















Some of my students are at loose ends at the moment.

I would like to task them with possibly adding this module.

May we help?


So...


Query

What should the workflow look like to check out 1-? items?


Pop up?

Field input?

Add a variable quantity field to /consumables/311/checkout   ?


T



—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.






 Comment 60: This is a badly needed feature. I wish upon a star that this will finally pull through.
 Comment 61: V5 is in beta now. That frees us up to do a lot of things, this included. 
 Comment 62: Is it possible to lay hands on beta v5? If yes, how can I enroll?

W dniu 01.09.2020 o 09:37, snipe pisze:
>
> V5 is in beta now. That frees us up to do a lot of things, this included.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub 
> <https://github.com/snipe/snipe-it/issues/5176#issuecomment-684518255>, 
> or unsubscribe 
> <https://github.com/notifications/unsubscribe-auth/AQHU7FRUDYUSWYGA34L7RU3SDSQDLANCNFSM4EUPRAFA>.
>

 Comment 63: +1
 Comment 64: +1
Would like to see this feature implemented as well 
 Comment 65: upgraded to snipe-it 5.1, but no sight of the requested feature😭
 Comment 66: Recently came across snipe-it and started working on it with an intention of implementing this in our department. Upgraded to snipe-it 5.1.5 yesterday too.

Really need this feature. Need to have the quantity field during the check out of consumables and accessories.
Otherwise it is a tedious task to repeat the checkout multiple times when it is required to lend some items in more than 1 quantity.
 Comment 67: Also have been waiting since 2018 for this feature, its gotten to the point I have stopped checking items out and am now instead modifying the total instead. Upside this also allows me to check unused consumables back in as well but defeats user tracking for checkout.
 Comment 68: From what I understand in September our dreams may come true with the release of v6
![obraz](https://user-images.githubusercontent.com/68112278/127974828-d817a879-2d25-485f-a738-b2b7a640dbc5.png)
:)
 Comment 69: > From what I understand in September our dreams may come true with the release of v6
> ![obraz](https://user-images.githubusercontent.com/68112278/127974828-d817a879-2d25-485f-a738-b2b7a640dbc5.png)
> :)

Sweet, though still cant check beck in TAT
 Comment 70: Looking forward to this capability along with barcode generation for consumables! Hopefully V6 will be the answers. Thanks for all the hard work and a great tool. 
 Comment 71: when you can add the feature to consumables check out? Thanks, so many users request it.
 Comment 72: Our online pay version is still v5.4.4 build 6829, when new version will update for all users?

domain.snipe-it.io

 Comment 73: @jonathanroots Just shoot us an email with your subdomain, we'll get you updated right away. mbell@example.com. We're doing a gradual rollout so as not to overwhelm the helpdesk but we're happy to upgrade on demand as well. :)
 Comment 74: https://rootsclinic.snipe-it.io/admin

 

 

rootsclinic

 

our domain www.rootsclinic.org <http://www.rootsclinic.org> 

 

 

 


   
Jonathan Huang  
Senior IT Manager
Roots Community Health Center
​9925 International Blvd.
​Oakland, CA 94603
T: 907.813.5593
www.rootsclinic.org
Healing Our Community From Within
The information contained in this e-mail, including any attachments, is confidential and intended solely for the named recipient(s) and may be subject to protection under federal and state laws. If you are not the intended recipient, please inform the sender immediately by reply e-mail that the message was sent in error and delete the message. Thank you.

NOTICE: This email message and/or its attachments may contain information that is confidential or restricted. It is intended only for the individuals named as recipients in the message. If you are NOT an authorized recipient, you are prohibited from using, delivering, distributing, printing, copying, or disclosing the message or content to others and must delete the message from your computer. If you have received this message in error, please notify the sender by return email.
From: snipe ***@***.***> 
Sent: Sunday, July 3, 2022 7:58 PM
To: snipe/snipe-it ***@***.***>
Cc: jonathanroots ***@***.***>; Mention ***@***.***>
Subject: Re: [snipe/snipe-it] Checkout Consumables Totals (#5176)

 

@jonathanroots <https://github.com/jonathanroots>  Just shoot us an email with your subdomain, we'll get you updated right away. ***@***.*** ***@***.***> . We're doing a gradual rollout so as not to overwhelm the helpdesk but we're happy to upgrade on demand as well. :)

—
Reply to this email directly, view it on GitHub <https://github.com/snipe/snipe-it/issues/5176#issuecomment-1173284299> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ2JWRMVZKO4PFRNLDJE5VTVSJHK7ANCNFSM4EUPRAFA> .
You are receiving this because you were mentioned.  <https://github.com/notifications/beacon/AZ2JWRJ55Q3AWLM7KWQ6CDLVSJHK7A5CNFSM4EUPRAFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIXXOLSY.gif> Message ID: ***@***.*** ***@***.***> >


 Comment 75: @jonathanroots i deleted your message for your privacy, but you’re all upgraded now :)
 Comment 76: Thanks,

We have one account for IT inventory already.

 

We are going to buy another account for medical inventory,  consumables, accessories to manage. 

 

I hope the quantity will be add to consumable check out.

 

Thanks,

 

Jonathan

 


   
Jonathan Huang  
Senior IT Manager
Roots Community Health Center
​9925 International Blvd.
​Oakland, CA 94603
T: 907.813.5593
www.rootsclinic.org
Healing Our Community From Within
The information contained in this e-mail, including any attachments, is confidential and intended solely for the named recipient(s) and may be subject to protection under federal and state laws. If you are not the intended recipient, please inform the sender immediately by reply e-mail that the message was sent in error and delete the message. Thank you.

NOTICE: This email message and/or its attachments may contain information that is confidential or restricted. It is intended only for the individuals named as recipients in the message. If you are NOT an authorized recipient, you are prohibited from using, delivering, distributing, printing, copying, or disclosing the message or content to others and must delete the message from your computer. If you have received this message in error, please notify the sender by return email.
From: snipe ***@***.***> 
Sent: Sunday, July 3, 2022 10:04 PM
To: snipe/snipe-it ***@***.***>
Cc: jonathanroots ***@***.***>; Mention ***@***.***>
Subject: Re: [snipe/snipe-it] Checkout Consumables Totals (#5176)

 

@jonathanroots <https://github.com/jonathanroots>  i deleted your message for your privacy, but you’re all upgraded now :)

—
Reply to this email directly, view it on GitHub <https://github.com/snipe/snipe-it/issues/5176#issuecomment-1173351427> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ2JWRNNHBN7JJKCCKAMWLDVSJWE7ANCNFSM4EUPRAFA> .
You are receiving this because you were mentioned.  <https://github.com/notifications/beacon/AZ2JWRNPM4DTD6CSJBFKN6LVSJWE7A5CNFSM4EUPRAFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIXX6YAY.gif> Message ID: ***@***.*** ***@***.***> >


 Comment 77: +1 for this really time saving feature!
 Comment 78: +1
 Comment 79: How can we use the new version 6 of snipe-IT on the website. Cloud 

 

Thanks

 

Jonathan

 


   
Jonathan Huang  
Senior IT Manager
Roots Community Health Center
​9925 International Blvd.
​Oakland, CA 94603
T: 907.813.5593
www.rootsclinic.org
Healing Our Community From Within
The information contained in this e-mail, including any attachments, is confidential and intended solely for the named recipient(s) and may be subject to protection under federal and state laws. If you are not the intended recipient, please inform the sender immediately by reply e-mail that the message was sent in error and delete the message. Thank you.

NOTICE: This email message and/or its attachments may contain information that is confidential or restricted. It is intended only for the individuals named as recipients in the message. If you are NOT an authorized recipient, you are prohibited from using, delivering, distributing, printing, copying, or disclosing the message or content to others and must delete the message from your computer. If you have received this message in error, please notify the sender by return email.
From: snipe ***@***.***> 
Sent: Sunday, July 3, 2022 10:04 PM
To: snipe/snipe-it ***@***.***>
Cc: jonathanroots ***@***.***>; Mention ***@***.***>
Subject: Re: [snipe/snipe-it] Checkout Consumables Totals (#5176)

 

@jonathanroots <https://github.com/jonathanroots>  i deleted your message for your privacy, but you’re all upgraded now :)

—
Reply to this email directly, view it on GitHub <https://github.com/snipe/snipe-it/issues/5176#issuecomment-1173351427> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ2JWRNNHBN7JJKCCKAMWLDVSJWE7ANCNFSM4EUPRAFA> .
You are receiving this because you were mentioned.  <https://github.com/notifications/beacon/AZ2JWRNPM4DTD6CSJBFKN6LVSJWE7A5CNFSM4EUPRAFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIXX6YAY.gif> Message ID: ***@***.*** ***@***.***> >


{'source': 'GithubIssues', 'repo_name_with_owner': 'snipe/snipe-it', 'issue_id': 303754020, 'repo_stars': 6959.0}