Snipe-it: Feature Request: Checkout Consumable to Asset

[wilsonlspacheco]

Expected Behavior (or desired behavior if a feature request)

Im IT Tech from a Hosted Customer ([redacted])
We've been reading issues #4927, #4597, #4582, #3507, #1538... but this (simple) feature apears doesn't exist yet.

We want checkout consumables to an asset (ex: printer), you can enable it? Its a very important feature to us and we believe that it's important for other people too.

---

Actual Behavior

Now i'm only able to checkout to user

---

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

• [ ] I have enabled debug mode
• [x] I have read checked the Common Issues page

---

Provide answers to these questions:

• Is this a fresh install or an upgrade?
  Hosted

• Version of Snipe-IT you're running
  v4.1.10 build 3249 (g8d3a214)

• Version of PHP you're running
  7.1.11

• Version of MySQL/MariaDB you're running N/A

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

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

[cslucian]

Hi you can add issue #4582 regarding the same subject

[snipe]

Duplicate of #4582

[wilsonlspacheco]

@snipe ..

You closed our ticket #4946 (marked "ready for dev") as "duplicated" with ticket #4582 that isn't marked "ready for dev" ? .. We know this ticket was duplicated, we refered all tickets with this feature request in our description, since Dec 29, 2015...

So.. whats the state of this feature now ? redy for dev or not?

[snipe]

@wilsonlspacheco Ready for Dev just means that the feature as a concept has been approved by the maintainers, so that if someone wanted to work on it, the idea has as least been vetted. It doesn't actually mean it's been started.

It's a ticket that gets duplicated frequently, and we just missed tagging it as ready for dev.

The feature itself isn't as simple as it seems, as we have a number of polymorphic relationships within the database. When it as first suggested, we hadn't switched to a polymorphic structure yet, so it was vastly more complicated, but even now it's not quite as simple as one might think at first glance. Code is impacted throughout the models, controllers, transformers, presenters and UI for this change, so it's not quite so small as it seems.

[Mynty100]

This feature would be perfect as we are in a school and have many shared/network printers.
Cheers.

[wilsonlspacheco]

@Mynty100 i agree, network shared printers is a normal and standard scenario in 90% of schools and companies.. !