Snipe-it: Feature Request: Create Asset/Consumable/Accessory from Purchase Orders

Created on 20 Nov 2017  Â·  65Comments  Â·  Source: snipe/snipe-it

Related to: https://github.com/snipe/snipe-it/issues/3394

  1. Introduce an element called "Purchase Orders" (or just "Orders"). On this element, capture:
  • Supplier
  • Asset Model/Consumable/Accessory (from existing items)
  • Qty ordered
  • Price per item
  • Date of order
  • Notes (optional)
  1. Auto-generate a Purchase Order number when a PO is created, of which the format is definable (via Regex maybe?) in the Settings menu.

  2. Allow this Purchase Order to be "Fulfilled"... when a PO is Fulfilled:

  • On Consumables/Accessories, the Quantity deployable is increased with the Qty on the PO on the existing items
  • On Asset Models, new Assets are created with default values for the amount of items on the PO; or maybe by displaying a page with a grid-like interface where each Asset to be created's fields can be modified before they are created; or, maybe asking for a CSV import as part of the Fulfillment with the details of each Asset? The Order Number field on the Asset should be pre-populated with the PO number, and this number cannot be changed.
  1. Allow a Purchase Order to be "Cancelled". Self-explanatory.

  2. Remove the Order Number field from Consumables and Accessories, as this is now contained in the PO.

  3. Allow a user to view the purchase orders related to an Asset/Consumable/Accessory in a grid on the View page (i.e. on http://mysniperserver/consumables/1, underneath the consumable Checkout details)

  4. Allow navigation from an Asset to the Purchase Order (since the Purchase Order number is present on the Asset and not changeable)

  5. (Nice to have) Allow a Custom Fieldset for Purchase Orders, i.e. to add a Payment Number, Delivery Date etc


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

feature request ready for dev

Most helpful comment

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!

All 65 comments

On Purchase Orders: Be able to attach supporting documentation like PDFs

This would be life changing amazing. I just started looking into trying to write this feature but quickly realised my laravel knowledge is terrible.

What has been asked in 1.) would be absolutely amazing. We really need a clean way to create purchase orders and add items to it as well as a quick way to print off purchase orders and their assigned assets for easy showing to auditors when the time comes.

We would need to be able to specify the order number's ID like in the existing order field as we have an internal PO number that needs to be matched.

would be nice to get away from lots of manual steps, could even have approval steps would make it amazing!!

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!

Please don't let this become stale! My comment stands that this is the only thing that is stopping me from being able to migrate to Snipe-IT.

I'd like this also. I now made a status "Ordered" and use that. But a having it seperate would be better.

I just want to add my voice to this feature request. We've started rolling out Snipe-IT and this is pretty much the only thing that is lacking.

Having to create new accessories (essentially duplicates), every time one needs to order new RAM, keyboards, mice etc. isn't the best way to be handling asset / inventory tracking. Editing the existing item isn't really an option either as you lose your order histories etc.

If anything is going to be prioritised as a new feature it really should be this.

I'll bump again my comment in the hopes that more people see the need ...

"What has been asked in 1.) would be absolutely amazing. We really need a clean way to create purchase orders and add items to it as well as a quick way to print off purchase orders and their assigned assets for easy showing to auditors when the time comes.

We would need to be able to specify the order number's ID like in the existing order field as we have an internal PO number that needs to be matched."

I echo the above. My components and accessories are turning out to be a mess as I now have so many duplicates. Each time a new order is placed we have to create a duplication of components and accessories so we can effectively track purchase histories.

Another nice to have would be to actually generate the PO document (i.e. "export" the PO element as a PDF file with a definable logo in Settings somewhere?) that can be sent to the Supplier.

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!

I really wish this feature was completed. It is so sad that after I have found this incredible software (snipe-it) that the brilliant and obvious suggestion (purchase order) to help push snipe-it past new horizons that it has not been completed as yet. Please guys lets get this going.....it is so close to being the perfect solution

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!

@yajmarshall as you can see by our release history, we are constantly pushing out new features. While this one is important to you, lots of other features are important to other people.

We appreciate your patience.

Shame. This one feature is holding us back from deploying organisation
wide.

On Tue, Aug 28, 2018, 8:39 AM snipe notifications@github.com wrote:

@yajmarshall https://github.com/yajmarshall as you can see by our
release history, we are constantly pushing out new features. While this one
is important to you, lots of other features are important to other people.

We appreciate your patience.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/snipe/snipe-it/issues/4488#issuecomment-416391952,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA1QD5zenQP5ZCzB-rI3Sg7qvEXqmA55ks5uVHU3gaJpZM4QkAaO
.

@JSzaszvari I'm sorry to hear that, but we're a small team. We work on things every single day, but there are only 24 hours in a day. Pull requests and/or bounties are always appreciated.

Hi snipe. Thanks for all your (and the rest of the team's) hard work on this amazing project. I hope you don't take away people's comments as being anything but a strong desire to be able to finally move to using Snipe-IT. The moment this feature gets developed I will erect a Mohawk-laden statue in your honour. :P

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!

Go away stale bot. It's still relevant.

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!

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!

why won't you just get this feature stale bit....tell em, it's a good
feature

On Sat, Dec 29, 2018, 5:12 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 were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/snipe/snipe-it/issues/4488#issuecomment-450481695,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aoxchw9hgRQMqwef69X9Kg24XFURHXvtks5u9z_zgaJpZM4QkAaO
.

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!

Any progress on this??
its the last piece of the puzzle

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!

Go away stale bot.

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!

we will not stop stale bot. It is a necessary and revolutionary feature

On Sat, Apr 20, 2019, 12:01 AM stale[bot] notifications@github.com wrote:

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 were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/snipe/snipe-it/issues/4488#issuecomment-485059029,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKGFZB4FUZVSD56JCUQPZSTPRKPRVANCNFSM4EEQA2HA
.

+1e10

+1

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!

It's still relevant.

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!

+1
This is still relevant.

Indeed, this ist still relevant.

This would be a really helpful feature for my organization. Additionally, on Purchase Orders, to be able to attach supporting documentation like PDFs.

+1
Definitely something that is still relevant and would be an amazing feature!

As others have said, very relevant.

gohomestalebot. We will never let you win.

+1 for this feature. My accounts team would love you forever♥

+1 this is absolutely needed.

+1. Simply for us is knowing what is ordered and when it should come in.

+1. Really important feature!

+1

This would be a game-changer for us too!

This would make consumables tracking make much more sense.

+1

+1

Any update on this feature request or any option to upload Purchase Order corresponding to as asset and view the same ??

+1

+1

+1 million!

This is a really basic and important feature. As an IT manager this feature is absolutely necessary. I can also say I am confident my organization will migrate to Snipe IT if it's implemented.

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!

Has a commit landed that fixes the issue stalebot? No? Then it's still relevant. Zark off.

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!

I agree on the relevance

Up vote

one more here, just setting an organization up with snipe and entering a large (for them) order, would be good to track this in one place like mentioned with the PDF upload of the order and associated assets.

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!

Go away stalebot, just coming back to say we're all watching this, and it is still relevant.

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 bet your bot it is still relevant

On Sun, Aug 30, 2020 at 8:51 PM stale[bot] notifications@github.com wrote:

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 were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/snipe/snipe-it/issues/4488#issuecomment-683510550,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKGFZB4PXSFDLXS4LPPRNVLSDL625ANCNFSM4EEQA2HA
.

--
Jay Marshall

I like this and subject to a bit of help - I'm happy to pay a bit for someone to get it moving so long as it isn't going to take up a lot of my life... So
a) Who is still interested in this FR (feature request)?
b) Will two people help with quality assurance?
c) Will two people help refine the initial request into an SRS and hand hold the developer(s) to get it done?
Thanks
Jason

@nLiveTeam I guess you can pay the developers directly and get it implemented.

Also this exists: https://www.bountysource.com/issues/51761795-feature-request-create-asset-consumable-accessory-from-purchase-orders?utm_campaign=plugin&utm_content=tracker%2F505106&utm_medium=issues&utm_source=github

Would be better if you get hold of the core devs and see what they respond with.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

snipe picture snipe  Â·  5Comments

snipe picture snipe  Â·  3Comments

ericdude101 picture ericdude101  Â·  5Comments

mauroaltamura picture mauroaltamura  Â·  5Comments

comisso picture comisso  Â·  4Comments