Feature request: Serial Number for each component.

igloo777 commented 7 years ago

Hello! Interesting to have possibility to add Components with serial number of each component. Example: i want to add 10 New Disk into Components, and i want to add serial number to each Disk. Later I want to connect each disk to dedicated asset Server. In "Components" of each Server i want to see exact Disk with it's serial number. The same logic can be applied to other kinds of components - Ram, CPU, Power supplies and so on. What do you think about it? Is it difficult to implement such logic?

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/39321543-feature-request-serial-number-for-each-component?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).

sainirahul commented 7 years ago

Hi Team, I also fell the same requirement that we can add serial number to component and accessories. It would be great to have such a feature. Thanks

dmeltzer commented 7 years ago

There is a serial number field added for components now, but it's one serial number for all instances of that component. The idea of components is that they are interchangable, and it doesn't matter which one you are using. The only items tracked individually at this point are licenses and assets.

igloo777 commented 7 years ago

Simple example: we have a good disks in work, good disks in reserve, broken disks in test, broken disks in a boxes, each one should have ID to track it's location and status. Disks are interchangeable, but still uniq. The same about RAM modules.

snipe commented 7 years ago

@igloo777 that's not currently how compoments are meant to work

chriswiggins commented 7 years ago

@snipe is there a usage example for how components are supposed to work? That would be much appreciated 👍

igloo777 commented 7 years ago

How we can see components in UI (sorry for my english):

when clicks to 'Components' menu, we enter into the page with a list of components (as it is today), it can be components by types or smth else.. (Component Name, Location, Category, Total, Min. QTY, Remaining, Parent Component, Actions and so on..)
next when we clicks on exact Component Name, we enter into the page with a list of components of the same type (for example Disk WD - parent component name) - list of fields: Component Name, Location, Category, Serial number, Status (or tag), Asset (connected to asset or blank), Parent Component, Actions
next, when we clicks to the name of exact component, we enter into the page with a detailed list of component attributes (fields) - same as it's done for assets

Posilan-Steve commented 7 years ago

I agree with @igloo777 - it woudl be great to allocate a serial number per component. You can have lots of components the same, but with different serial numbers (think hard drives etc) but i cant think of any situation where more than one component would have the same serial number (surely they are always unique to that piece of hardware)?

Hickory420 commented 7 years ago

Hello, so I have a question... First, an example: Components are: cpu, ram, gpu, psu, and motherboard. Asset is the server chassis (all components combined). Each component technically has a unique serial number....

So what would be the current "workaround" for this this instance? If we switch the components to assets, then we can no longer assign the component (now labelled as an asset) to an actual asset. Any thoughts or suggestions?

Cheers.

kiltain commented 7 years ago

Tracking Components with serial numbers would help; in my company assets are all tagged items such as laptops and desktops, anything over $1000. I would love to be able to have a docking station be able to be a component that is assigned to an asset and provide a unique serial number. i have 15+ units of each dock and would like to track them but still have them listed under a single component heading. Thank you.

PhantomPhreak commented 7 years ago

I'm trying to start using Snipe-IT now, but there some things that doesn't meet my requirements: components and accessories management.

As i can see on the Component's creating page, "Components are items that are part of an asset, for example HDD, RAM, etc.", but i want to track these items (HDD, RAM, etc) by serial number (or inventory number), and i want to have serial number (and inventory number too, optionally) assigned to each component. But as i can see there is only one serial number for bunch of components. Honestly, i'm confused how a lot of components may have one serial?

The same for accessory. For example, i have IP-phones, it's accessories, and i want to manage them too, separately, but i can't create SN or inventory number for each device. This problem described in #3408

Also, i'd like to have possibility to group my components/accessories, because flat structure isn't convenient for components managing. For example, i'd like to have group "WD 2TB Black" in HDD category, with a list of components inside.

It would be great to see this features in Snipe-IT.

Thanks a lot!

igloo777 commented 6 years ago

Hi Snipe-IT developers! I'm glad that you are working hard on this product. Still waiting this feature to start to use Snipe-IT.

One more this feature usage example: We can have asset in work - switch Cisco Catalyst 6807-XL than contains the next components:

Cisco Catalyst 6807-XL chassis
Cisco Catalyst Supervisor Engine C6800-SUP6T
Cisco module WS-X6908-10G-2T

Also we can have a spare modules in cold reserve. Each component in example should have it's own Serial Number, to be tracked.

PhantomPhreak commented 6 years ago

I agree with igloo777. Components are not consumables (checkout and forgot) and may be really expensive hardware (like network modules in previous example), and may have it's own warranty. Also, components may have different states: ready for use, in test, in maintenance/warranty and so on. At my glance it's more important than for assets. If power supply or hard disk fails in a server (server is an asset), we're not changing whole server (not changing asset state), but changing failed part (component). That's why it's really important feauture to tack each component by serial. And it should be a key feature. Unfortunatelely, without this feature we can't start using Snipe IT.

Still waiting for it. Thanks a lot!

cslucian commented 6 years ago

Hello,

Maybe the following workflow will work for you

Create components only with qty.1 so if you have 10 hdd create 10 new components.

Maybe devs. can implement the auto increment feature from Asset Tag to have unique tags for each component.

In this way you can enter the Serial Number for each component and assign them to assets.

Best of luck

PhantomPhreak commented 6 years ago

It can work, but it looks like workaround and: 1) We will loose the feature of grouping the components by type. For example, i would like to group disk drives by the model for better organizing. See (https://demo.snipeitapp.com/components) 2) We will loose the feature of tracking amount of components of each type, and set the lower threshold for each type of components. 3) We will have to set some excessive information about the component (company, purchase date, cost, etc.) 4) We will have to checkout the components to assets one-by-one, not by a bunch of components (16 RAM modules to the server for example), it will be quite annoying in web interface and quite tricky using provided API

So, i don't think that it's a good solution of our problem but anyway, thanks for suggestion!

mario-tremblay commented 6 years ago

the lack of this feature is a deal breaker for me too.

i want to be able to add multiple ssd harddrives of the same model with all their own serial number but want it to count for the minimum quantity alert

plz plz plz make it happen :D btw great work so far.

Puddl36lum commented 6 years ago

+1 for a usage example.

We have just purchased 10 internal hard drives, All the same model (WD10EZEX), each with different serial numbers.

can't input as assets because we don't have asset tags on most internal components and the asset tag field must be unique. Would also prefer not to input 10 of the same model drives as individual components.

wilsonlspacheco commented 6 years ago

+1 to our company (Snipe-IT Hosted Client)

We bought a lot of accessories and components with S/N, it was important to us be able to manage the serial numbers. Or, in the limit, like the licenses, have a field of notes to put the serial number when we check-in the Accessory / Component to a User/Asset and can see the history of this accessory in a table with the notes field visible. It is also an alternative solution to us.

hostbrew commented 6 years ago

This feature is highly desirable. A big deal breaker for me as well.

Hickory420 commented 6 years ago

A year and a half later, and still no sign of this happening... what a shame. @snipe do you have any plans to listen to your user base/the community? Is this something we can expect, or are we holding our breath?

Cheers.

PhantomPhreak commented 6 years ago

I'm tracking snipe-it releases and there are a lot of new fancy features. But all they are useless for me without this simple, but basic feature for hardware accounting.

dmeltzer commented 6 years ago

@Hickory420 I'm sure if it were terribly important to someone they would have taken the few hours to contribute the feature to the codebase, it's one of the beautiful things about open source software, after all :)

snipe commented 6 years ago

@snipe do you have any plans to listen to your user base/the community? Is this something we can expect, or are we holding our breath?

@Hickory420 Perhaps you've not been paying attention, but we ship new features constantly - certainly faster than most open source projects. To suggest I don't listen to the community is, frankly, offensive and obnoxious - and certainly not the way to inspire us to work on a feature any faster.

This is a non-trivial change to the business logic, and it's on the list, but so are hundreds of other feature requests.

Hickory420 commented 6 years ago

To suggest I don't listen to the community is, frankly, offensive and obnoxious - and certainly not the way to inspire us to work on a feature any faster.

@snipe I apologise for coming across as offensive and obnoxious. That was not my intention. I was just a little frustrated when I wrote that. I'm sorry. This is an excellent open source project. I have implemented it a while ago in the company I work for, and everyone who uses it, loves it. So, I thank you very much for all of your efforts, it is very much appreciated. :)

This is a non-trivial change to the business logic, and it's on the list

Awesome :)

@dmeltzer I think I speak for most of the users when I say, If I could, I would! :P

To everyone who has contributed to this project, we thank you! <3

rkantos commented 6 years ago

@Hickory420 Working for a company, using Snipe-IT with it. I hope you have made at least some kinds of calculations on how much Snipe-IT has saved for you? Maybe there would be something you could contribute too.. Perhaps consider Bountysource ;) https://www.bountysource.com/teams/snipe-it/issues

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!

WisdomPanda commented 6 years ago

+1 for this feature, doesn't really make sense to have components the way it is currently.

Blizzardo1 commented 5 years ago

I have a custom Inventory System at work that works the way it should be, every element has a serial number bound using a component item in store. This means each element inherits from the root component.

For Example, the Component (Seagate 1TB HDD) has 30x Elements with their own serial number, that way we can track where the drive is, whether it's currently in a machine, or in our inventory's Available, Re-Inventory, or RMA. The problem with the system I have is that I can't necessarily keep track of other components that are not trackable via serial number such as but not limited to Power Cables, Converter Trays, Keyboards, Mice, etc.

The way I saw SnipeIT is that I can associate a component via serial number to a device, however, it's only an internal serial number and not tracked by the component's true unique number.

Since this Platform is Open Source, My Dev Team would be able to add such a feature, but out of the box, however, I see that other people in this thread are talking on the same page as I am.

niteowl099 commented 5 years ago

This issue is listed as closed, does that mean it has been implemented or is it something that is no longer being considered for development?

I am still very much interested in this feature.

Thank you

nielsentamau commented 5 years ago

I am still very much interested in this feature.

Same.

PhantomPhreak commented 5 years ago

I talk to snipe-it support about it. They said that they won't and have no plans to implement this feature. That's absolutely incomprehensible for me how they still can do fancy features missing this basic functionality

rkantos commented 5 years ago

Wouldn’t the custom fields functionality work here? You could have a text area with any formatting necessary for listing serial numbers: https://youtu.be/AmKc0GuQbAU?t=2m7s

YouTube
Snipe-IT Turbo Tutorial: Custom Fields
Become an expert in handling custom fields for assets in about 7 minutes with our first-ever user tutorial. Forgive Alison - she's a nerd, not a voiceover ar...

PhantomPhreak commented 5 years ago

Wouldn’t the custom fields functionality work here? You could have a text area with any formatting necessary for listing serial numbers: https://youtu.be/AmKc0GuQbAU?t=2m7s

YouTubeSnipe-IT Turbo Tutorial: Custom FieldsBecome an expert in handling custom fields for assets in about 7 minutes with our first-ever user tutorial. Forgive Alison - she's a nerd, not a voiceover ar...

Possibly, it will. But currently custom fields are apllicable for Assets only (see from 5:55 in the video you attached), so here is a feature request (opened since october 2017) https://github.com/snipe/snipe-it/issues/4261

YouTube
Snipe-IT Turbo Tutorial: Custom Fields
Become an expert in handling custom fields for assets in about 7 minutes with our first-ever user tutorial. Forgive Alison - she's a nerd, not a voiceover ar...

bl00d666 commented 5 years ago

I think this is a very important feature. We were about to use the system. We had high hope for it, but this is a deal breaker for us. Hey Dev (@snipe), you have done a great job with the system. We really like it. I just don't know how we could manage our inventory without having component with multiple item and serial number in it. Just for the purchase date and warranty alone it's a deal breaker. Having a single component for each serial will also make the asset more complicated to use and will make the threshold irrelevant. I hope you will reconsider the feature.

edit: we just check, and we will try using the asset and component to manage our system. adding every hardware as asset so we have their serial and purchase date, but we will create more generic component (like gtx 1060 graphics card x 20) so we can assign component to pc asset, and still be able to have the threshold of different hardware. so might not be a deal breaker as i tought at first

Hickory420 commented 5 years ago

Feature request opened on Nov 17, 2016.

Quoting @snipe from May 8, 2018

This is a non-trivial change to the business logic, and it's on the list, but so are hundreds of other feature requests.

Quoting @PhantomPhreak less than a month ago.

I talk to snipe-it support about it. They said that they won't and have no plans to implement this feature.

I am so confused... If it's non-trivial, why hasn't it been implemented yet? I'm not having a shot at the devs. It's a genuine question. This is a hugely popular request. Is it a technical issue, or something else?

PhantomPhreak commented 5 years ago

Hi,

Unfortunately, that is not on our roadmap for the near future, so you may have to go elsewhere to be able to use this feature right away..

Sorry we're not able to be of more help at this time : /

Sincerely,

Victoria Pak Operations & Support Engineer Grokability, Inc. support@snipeitapp.com 844-4-SNIPE-IT (844-476-4734)

3960 West Point Loma Blvd | Suite H69 | San Diego CA 92110

@Hickory420 just go elsewhere to be able to use this feature right away..

Blizzardo1 commented 5 years ago

In all honesty that's terrible support.

I would rather use community driven software instead of an enterprise... this is horrible.

captains1stm8 commented 4 years ago

I would like to see this feature added, as well. Monitors, for example, are components. I need to know the total number of each model that we have, but I also need to keep track of serial numbers for warranty purposes.

Hickory420 commented 4 years ago

Over three years later and still not listening to the community... And apparently (quoting the project owner here)

@snipe

a non-trivial change to the business logic

is too much to ask for...

I've given up on this software. I just like too see how long this will go for. 3 years and counting :P

clifforddsouza commented 4 years ago

Another 3 years have past by and still no signs of a non-trivial change to the business logic being implemented.

I've also given up on the software, it's sad that a basic necessity as this is being ignored for so long

hope this gets implemented

djmixman commented 3 years ago

Bringing this in for the new year... I don't understand the logic behind having 42 hard drives with the same serial number. It does not make any sense to me what so ever.

Hickory420 commented 3 years ago

I have been watching this thread for a while. 5 years for a 'non-trival' change. There is some humor in watching an open source project ignore its user base. Also sad to watch. I only follow this issue to see how long it takes before this project dies or this feature gets implemented. I'm betting on the former.

To anyone looking for asset management software, don't waste your time with this.

TerraTech commented 3 years ago

(NOTE: I just started using Snipe-IT today, so still learning)

I see the "component" has a place to enter a serial number, but what would make it easier to add multiple HDD/SSD is the ability to Duplicate (or Clone) a component and then just paste in the new serial number + Save. I think this would make for a somewhat quick interim solution, that can be retained even after the above feature request is implemented.

I have not yet explored the API or Import feature yet - however from a GUI standpoint, "Duplicate" would be useful.

If others agree, I could add this as a new feature request.

KevinWirth93 commented 3 years ago

@snipe you wrote that's not currently how compoments are meant to work.

Could please explain it to me how the componentes are meant to work ?

Right now it makes no sense to me not to have an individual serial number for e.g an HDD for a server.

So is it meant to create one component for each individual serial number ?

best regards

Kevin

gabriel-vanca commented 2 years ago

This is still not fixed 6 years later. Shocking.

snipe commented 2 years ago

@gabrielv33 I welcome your pull request.

Hickory420 commented 1 year ago

https://github.com/snipe/snipe-it/issues/2934#issuecomment-890918877

@snipe you wrote that's not currently how compoments are meant to work.

Could please explain it to me how the componentes are meant to work ?

Right now it makes no sense to me not to have an individual serial number for e.g an HDD for a server.

So is it meant to create one component for each individual serial number ?

best regards

Kevin

This person has genuine questions... I wonder what the reply is...

🍿

snipe commented 1 year ago

@Hickory420 - as I mentioned earlier in this (very long) thread, just track is as an asset. Components are bibs and bobs, where serials don't matter. Just track it as an asset. Make a category for it, track it that way, and move on.

snipe / snipe-it

Feature request: Serial Number for each component. #2934