Checkout Consumables Totals

devkingkong commented 6 years ago

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

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

chaaza commented 6 years ago

I agree with this.

dangerd1 commented 6 years ago

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

stale[bot] commented 6 years ago

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!

stale[bot] commented 6 years ago

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!

viclou commented 6 years ago

+1

st3llar commented 6 years ago

This. Please. :)

okarjun commented 6 years ago

Please add this features.

bveina commented 6 years ago

+1 especially for reams of paper. our copier takes 6 or 7 to be full. im currently not tracking paper for this reason

asfanet commented 6 years ago

nned the bulk Checkout Consumables, pls :D

acamporat-ga commented 6 years ago

I need this feature, please. I am trying to keep up with business audits.

hatimdegani commented 6 years ago

```

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

ckupris commented 5 years ago

Another vote for this, would be really handy

hatimdegani commented 5 years ago

Please help me out here @snipe @chaaza

snipe commented 5 years ago

@hatimdegani it’s in the roadmap, but we haven’t had a chance to work on it yet.

hatimdegani commented 5 years ago

Thank for replying

hatimdegani commented 5 years ago

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.

tymik commented 5 years ago

+1, this can also fit for stuff like patchcords for networking teams - totally must have! also the same should be for accessories.

dnyt84 commented 5 years ago

+1 vote for me as well.

thebigmick commented 5 years ago

hey guys I would like to add my voice to the masses begging for this feature. I too have to check out multiple consumables at once. Thank you for adding this to the feature request list.

XZF0 commented 5 years ago

... 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.

snipe commented 5 years ago

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, 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.

XZF0 commented 5 years ago

… 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, 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

trmz commented 5 years ago

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 ?

anddek commented 5 years ago

I also miss this feature a lot. Bulk checkout would make handling of consumables so much easier. Please consider to add this. Thank you.

perezalvarezhi commented 5 years ago

bump.

@hatimdegani it’s in the roadmap, but we haven’t had a chance to work on it yet.

Thank you!

perezalvarezhi commented 5 years ago

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 :(.

stale[bot] commented 5 years ago

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!

kamwai commented 5 years ago

i still need this feature or workaround to checkout quantity more than 1

stale[bot] commented 5 years ago

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!

thebigmick commented 5 years ago

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] notifications@github.com Sent: Tuesday, August 27, 2019 1:27 PM To: snipe/snipe-it snipe-it@noreply.github.com Cc: Michael J. Sweeney Michael.Sweeney@epcusa.com; Comment comment@noreply.github.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 GitHubhttps://github.com/snipe/snipe-it/issues/5176?email_source=notifications&email_token=AKWGDUQAKVHPLOCKUOATTTTQGVWX3A5CNFSM4EUPRAFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5IVZBI#issuecomment-525425797, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKWGDUWV2APGQCYGDVVX7C3QGVWX3ANCNFSM4EUPRAFA.

Michael Sweeney IT Manager 3941 Harry S Truman Blvd St Charles, MO 63301 Office: 636-443-1999 Fax: 636-443-1998 Email: Michael.Sweeney@epcusa.com mailto:%20Michael.Sweeney@epcusa.com [EPC] EPC, Inc. - Established in 1984 A wholly owned subsidiary of CSI Leasing, Inc.

www.epcusa.comhttp://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

stale[bot] commented 5 years ago

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!

geoakkawi commented 5 years ago

+1 for this feature, I would add that we should be able to put a default qty to check out in the setup

stale[bot] commented 5 years ago

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!

kamwai commented 5 years ago

+2, can't deploy snipe it until this feature is added, as there is no other workaround

gbarany commented 5 years ago

+1 for this feature, I would make a huge positive difference in our workflow

ntdan commented 5 years ago

Can i code it admin?

ntdan commented 5 years ago

I start using snipe from Oct 2018. It's very nice tool for it asset managemnet.

geoakkawi commented 5 years ago

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 ?

Eina61 commented 5 years ago

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!

stale[bot] commented 4 years ago

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!

kamwai commented 4 years ago

Yes, we still cannot deploy until this is enabled

On Jan 20, 2020 10:33 AM, "stale[bot]" notifications@github.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 GitHubhttps://github.com/snipe/snipe-it/issues/5176?email_source=notifications&email_token=AGBSOSZWTNZ6BPOSUIWJVJLQ6UEQHA5CNFSM4EUPRAFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJLFEBQ#issuecomment-576082438, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGBSOS4S6IY2PCQ4OEUURX3Q6UEQHANCNFSM4EUPRAFA.

stale[bot] commented 4 years ago

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!

bwmedien commented 4 years ago

Any idea, whether an implementation is possible this year? Thx!

alfiewild commented 4 years ago

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.

veenone commented 4 years ago

would love to see this feature coming as well :)

stale[bot] commented 4 years ago

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!

geoakkawi commented 4 years ago

It is still relevant

stale[bot] commented 4 years ago

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!

bwmedien commented 4 years ago

Not relevant for me anymore, I opted for another software because of it. Am 25. Apr. 2020, 14:36 +0200 schrieb stale[bot] notifications@github.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.

geoakkawi commented 4 years ago

Not relevant for me anymore, I opted for another software because of it. Am 25. Apr. 2020, 14:36 +0200 schrieb stale[bot] notifications@github.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?

snipe / snipe-it