Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checking a Consumable Out to an Asset/Location #10066

Closed
tsdigital opened this issue Sep 9, 2021 · 3 comments
Closed

Checking a Consumable Out to an Asset/Location #10066

tsdigital opened this issue Sep 9, 2021 · 3 comments

Comments

@tsdigital
Copy link

Snipe-IT Version

v5.1.8 build 6257 (gb5bb74b8c)

Operating System

Snipe-IT SaaS

Web Server

Snipe-IT SaaS

PHP Version

7.3.23

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

The biggest problem is that people aren't always the ones using consumables. Printers utilize paper and toner. It's hard to associate the usage of a consumable like paper to a single user for something like an MFP.

Describe the solution you'd like A clear and concise description of what you want to happen.

Assigning/checking out a consumable to location or asset would be ideal. It would also help to track which printers are incurring the most "maintenance" without just pulling print counts on each printer.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

A service user in Snipe-IT is what we have been using, but we only have a single service account. I have been tempted to create a service account for each printer, but I felt that could create a maintenance nightmare later.

Additional context Add any other context or screenshots about the feature request here.

This has been requested in the following places - #10057, #9760, #9164, #8976, #8763, #8912, #8272, but did not look to be listed as Feature Requests.

@welcome
Copy link

welcome bot commented Sep 9, 2021

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

@francogp
Copy link

#10057

@snipe
Copy link
Owner

snipe commented Sep 11, 2021

Closing as duplicate of #9760, #9634, and #10057

@snipe snipe closed this as completed Sep 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants