search

snipe / snipe-it

A free open source IT asset/license management system
https://snipeitapp.com
GNU Affero General Public License v3.0
10.92k stars 3.16k forks source link

Create Component has mutiple Quantity but one Serial (Possible Feature Request?) #4421

Open Iantull opened 6 years ago

Iantull commented 6 years ago

Expected Behavior (or desired behavior if a feature request)

When creating a component, I can add multiples of that component in Quantity, but in Serial, this is just a text field that I am assuming is for a singular entry. What would be great is to allow multiple serial for each unit (as per quantity entered), so entering 6 in Quantity would allow you to enter 6 Serial Numbers in Serial. On check out to an asset, you could when checking out the component be able to have Serial as a drop down box and select the one you want to checkout to the asset.

(what you expect to happen goes here)

Actual Behavior

Currently you can create a component, have multiple in Quantity, but the Serial Field is just a text field. When doing a checkout, it only shows, Component Name, Select Asset, then Qty.

(what actually happens goes here)

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

Provide answers to these questions:

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

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/51425785-create-component-has-mutiple-quantity-but-one-serial-possible-feature-request?utm_campaign=plugin&utm_content=tracker%2F505106&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F505106&utm_medium=issues&utm_source=github).
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!

duel007 commented 6 years ago

Just commenting to mention this is an important item for me as well, it would be very helpful to be able to do this.

joepitt91 commented 6 years ago

I would find this feature helpful too, I was just about to raise the same Feature Request, then found this one.

I find the whole Component page a bit contradictory, As soon as you have Qty and Min Qty, the following fields should probably be available for each one of that component

This feels like the best approach, over having to manually add the same component lots of times to accurately record these details.

stale[bot] commented 6 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!

Iantull commented 6 years ago

This can be closed

Regards Ian (VK2HK)

On 28 Jul 2018, at 6:05 pm, 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 authored the thread. Reply to this email directly, view it on GitHub https://github.com/snipe/snipe-it/issues/4421#issuecomment-408591031, or mute the thread https://github.com/notifications/unsubscribe-auth/AHmrvsfNIfZeQF75RaoJgDA8JmjiqXehks5uLBs3gaJpZM4QaWzC.

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!

stale[bot] commented 6 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!

joepitt91 commented 6 years ago

still needed

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!

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!

clifforddsouza commented 5 years ago

This is certainly relevant.... @joepitt91 comments make perfect sense... there is absolutely no point in having a hardware inventory system, if we cannot identify every component uniquely

Loved this software, but unable to put it to use because of this feature not available Thanks

Clifford Dsouza

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!

koshia commented 5 years ago

I also would like this feature. I have computers and larger equipment that are classified as assets. When adding memory, flash drives, or whatever else that's smaller and component-like, I like to have the minimum QTY and how many we have in stock - at the same time, the option to add unique serial to each component so I know where it's checked out to.

luis-nagaki commented 5 years ago

Same here, would love this feature to add serial # when checking out a component.

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!

duel007 commented 5 years ago

Still relevant.

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!

clifforddsouza commented 5 years ago

Absolutely relevant! , please develop, its the only feature that stopped me from using the product for our desktop asset management i could not add different RAM with different serial numbers to my Desktop asset!

Regards Clifford Dsouza

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!

duel007 commented 5 years ago

Still relevant

On Wed, May 29, 2019 at 4:18 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 are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/snipe/snipe-it/issues/4421?email_source=notifications&email_token=ABLC6M42T7FGLABN56RBL63PXZC65A5CNFSM4EDJNTBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWOWX7Y#issuecomment-496856063, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLC6M7T3HN7BXZ44DIKQATPXZC65ANCNFSM4EDJNTBA .

-- Matt Ware 712-310-6217 mattj.ware@gmail.com

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!

SoarinFerret commented 5 years ago

I agree this would be quite useful.

As a work around for right now, I am keeping the serial numbers for my HDDs in the "notes" section of the asset they are being assigned to. Not ideal, especially when they move between assets, but it at least gets the job done

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!

luis-nagaki commented 5 years ago

yes

Sent from my iPhone

On Aug 2, 2019, at 9:55 PM, 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 GitHub, or mute the thread.

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!

jonathanspw commented 5 years ago

Still relevant.

captains1stm8 commented 4 years ago

I just commented on another thread that was closed and then found this one.

This feature is actually a deal breaker for my company. We need to keep track of the total number of components that are available, but we also need to have unique serials attached to each for warranty purposes.

I am currently updating our home grown inventory solution AND an instance of Snipe-IT, in hopes of the feature being implemented so that we can move completely to Snipe-IT.

Please consider this during development.

Thanks for all the work that's been done :)

Hickory420 commented 4 years ago

@snipe This has been a request, in total for about 3 years. Multiple tickets opened about this feature and as you put it, it's a "non trivial change to the business logic".

And you told me you listen to your community... what a laugh.

ivankozlik commented 4 years ago

Soo why this feature isn't implemented jet? This is like a core feature that I need and many others. I don't understand the logic behind not implementing it ASAP.

Thank you!

ivankozlik commented 4 years ago

Hi! Just wanted to answer the question "Why don't we create components like assets?".

By my understanding asset is something that can work on its own. So HDD|CPU|RAM is not an asset and I cannot just give someone HDD|CPU|RAM since he/she cannot use it on it's own. That's why this is a component. Many components can make an asset (like when building a custom PC).

Please add this feature of when you're adding components and you set Qty to 10, to be able to put in 10 serial numbers and on save that should create 10 components with each serial number separated. When I'm building an Asset, I would then add/assign (preferably scan with barcode scanner) each component to that asset so that I know what exact component is in that asset.

Can we at least get some detailed explanation from snipeit team why is this such a problem, or why won't you put that in plans for implementing this?

Thank you!

lonczy commented 4 years ago

+1 for this.

I'd like to see a Component with a list of serial number/purchase date/ etc.

Would like to set the minimum quantity of that Component, so We can be sure to order if it fell under that minimum.

It would be also nice to have a location for the component. As a use case for that, we have 2 locations, and a few people roaming around with some spares in their cars, so if an issue comes they can fix the asset asap. so if a component is with someone, they can check it out, and that's fine, but with multiple locations, it would be nice to track which component is where, so you can reorganize if it is almost empty at one spot, and we have a lot of it on the other.

Also please note that we'd need the serial also at the checkout.

This might be resolved by having component types and components, so I could add a new type (like a specific router board or lte module), and then have multiple components of that type.

clifforddsouza commented 4 years ago

there are other posts requesting the same feature for so long now

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!

captains1stm8 commented 4 years ago

Definitely 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!

dbinoj commented 4 years ago

I would also like to have this feature / functionality in components! Will help a lot in making snipe-it a compelling alternate for many companies!!

uFojun commented 4 years ago

+1

Deployed this wonderful product in less than a week and the lack of this feature became a stumbling bloc

jonathanspw commented 4 years ago

I'm wondering why this hasn't even been acknowledged yet by @snipe while she does close other requests citing the same thing as duplicates of this one.

@snipe what kind of bounty is needed to get this implemented?

captains1stm8 commented 4 years ago

I'm wondering why this hasn't even been acknowledged yet by @snipe while she does close other requests citing the same thing as duplicates of this one.

@snipe what kind of bounty is needed to get this implemented?

A bounty, yes! So what’s the number, @snipe ? :)

pbrink231 commented 4 years ago

I was working on quantity tracking from this issue: #5581, for our company. Stumbled on this issue and wondering how this would affect what I am adding.

I understand why components exist now but really all of our components can be one of 2 things

So here are the possible situations. 1) Add model to component We add "Asset Model" class to a component. You can then create multiple components with the same model and a quantity of 1. You can track individual components then and see over all information on the asset model about component totals. Goods

2) Remove component, use Asset & Accessory

3) Making a individual tracking on component This is what it sounds like most people want. I come from manufacturing background so components make perfect sense to me but I think this method here is duplicating the system a bit and adds complication.

Summary Based on how the system is now going with option 3 would add a lot of complication when all of it has already been created for assets already with all the features of the system. Option 2 I think would be the best for the future but would need option 1 as a stepping stone and transition logic in place but very doable. Although this sounds like an easy add, this is definitely a large undertaking.

I am curious what people think of these solutions because we have similar issues in our company and want to solve them. Right now using Assets and Components. But want to add Accessory checkout to Asset and location also and will move components at that point to accessories.

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!

captains1stm8 commented 4 years ago

Still relevant. It’s a much needed feature.

Thanks!

On Sat, May 2, 2020 at 3:28 PM 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 GitHub https://github.com/snipe/snipe-it/issues/4421#issuecomment-623002308, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG7CN7CAKYC6VETCWQ6JCMDRPRX6LANCNFSM4EDJNTBA .

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!

zegelin commented 4 years ago

Would like to see support for multiple serial numbers/locations per component as well.

Also seemingly contradictory is the Purchase Cost field when combined with Quantity. Is this the total cost, or singular cost? Either way, after assigning a subset quantity of a component to an assets, the asset's Components page shows the full Purchase Cost verbatim, regardless of the quantity assigned:

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!

dbinoj commented 4 years ago

@stale, Yes!

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!

clifforddsouza commented 4 years ago

Wow! I gave up on this software in 2017 just because you lacked this feature and was hoping you would get this implemented,

This was THE feature I needed to get this software implemented for our organization.

ggiesen commented 4 years ago

This feature is important for me. We just bought a year of hosting and I can't believe this was implemented this way. Components need to be individually trackable by serial number. Having one serial number for a quantity of 10 makes no sense. If I create a separate component for each (so that I can track serial numbers), then I have no way to evaluate stock levels.

luis-nagaki commented 4 years ago

Wow i requested this almost 2 years ago and still no movement.

On Tue, Sep 15, 2020 at 11:56 AM ggiesen notifications@github.com wrote:

This feature is important for me. We just bought a year of hosting and I can't believe this was implemented this way. Components need to be individually trackable by serial number. Having one serial number for a quantity of 10 makes no sense. If I create a separate component for each (so that I can track serial numbers), then I have no way to evaluate stock levels.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/snipe/snipe-it/issues/4421#issuecomment-692809967, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLN5UUADITCXGEPKX243MDSF6FCZANCNFSM4EDJNTBA .