snipe-it
snipe-it copied to clipboard
[Feature Request] Check out multiple accessories/consumables at once
Quite often, we will check out a bunch of accessories (Power cables, power supplies, ect) and give them to a technician, who will then keep them in their stockpile (Checked out to them). Since we have a large number of users, we will just have a dummy user for "Deployed in the field". Right now, if a tech wanted to grab ten power cables and power supplies, they would need to click a "Check out" button 20 times. If they wanted to then assign all of them to the dummy "deployed in the field" account, they would also have to do each one individually.
It would be very useful if there was a "Quantity" field for when you check things out as well as some way (Checkboxes or otherwise) to check in multiple items at once.
why was this removed? Such a great plus for our inventory
I would love this feature as well.
This would be great. It might naturally follow that the list of a given accessory checked out to an individual would be consolidated to a single line item per individual.
Any plans to bring that up?
+1 on this. Need a quantity field at check out. Often we check out a switch (asset) with dozens of patch cables (accessories). we typically don't track location/user for accessories, but we do track quantity.
@Trog3r #1046 is this one, and it is open.
@snipe Excellent! I retract my comment and apologize for my confusion :(
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!
Hello Snipe Team, we just started exploring this system and are utterly impressed by it. Exemplary work, thank you so much.
We also, very quickly, ran into a situation where we wanted to check out multiple consumables and/ or accessories, so adding this feature would be very welcome.
this seems like such a simple request, however I am disappointed to see that this was opened in 2015 and still no traction on this?
@snipe is there anyway this can be opened and ignored by the stale rule. This seems like a super requested feature and I have bounced through so many chains with the same thing.
@snipe Could really do with this option right now! I have USB pen drives as consumables and departments/users take 5/10/20 at a time! Having to do the same checkout 20 times is a real ball ache! Any chance this feature could be added? #1046
stalebot this is still relevant
It's annoying to have to check out dozens of patch cords separately.
We give hundreds of mice and headphones to our teachers each year. Checking out 30 headphones at once to a teacher would be fantastic.
Any news for this request ? Would really like to be able to assign 1 item to multiple people.
Any news for this request ? Would really like to be able to assign 1 item to multiple people.
That's not on the roadmap, and I'm not sure what the use case for that would be, but it would be a different issue anyway.
Again, apologies - stalebot is configured to never auto-close issues that have "feature request", etc tags associated with them, but it can be a bit aggressive for some reason, despite the config file we give it. :(
This has never fallen off our radar, and we're working through a PR right now that might solve for this original issue WRT quantities.
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 can do this by entering the next file /resources/views/consumables/checkout.blade.php and placing this code
<!--Cantidad --> <div class="form-group"> <label class="col-md-3 control-label">{{ trans('general.qty') }} <i class='icon-asterisk'></i></label> <div class="col-md-9"> <input class="form-control" type="text" name="cantidad" id="cantidad" style="width: 70px;" value="1" /> </div> </div>
and then in the file app/Http/Controllers/Consumables/ConsumableCheckoutController.php add the following
public function store(Request $request, $consumableId) { for ($i = 1; $i <= $request->input('cantidad'); $i++) { … código existente } }
For anyone scrolling through this thread there is a pull request for this feature.
MetricMoose opened this issue on Aug 11, 2015. And it's now Dec 3, 2023. After 8 years, this issue is still open...., I really cannot image that.