snipe-it
snipe-it copied to clipboard
snipe
Custom Fields for Non-Assets (Licenses, Accessories, Consumables, Components, Users, Models, etc)
This has been proposed multiple times in various tickets, but I'm going to use this as a placeholder for that discussion moving forward, since the work behind extending custom fields beyond assets is basically the same, and would be a system-wide change.
I'll be closing all of the other related tickets and directing everyone here moving forward, as this issue will be easier to search on since it contains everything.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
I pulled this one out of #2411 so it doesn't get lost. I know it's talking about more than just custom fields. Do you want me to open a new issue for it?
- It would also be great if there could be some history included that can be included for license renewal. At the moment we are thinking of using the comment field.
This has actually turned out to be an all important need for us. We need to track license purchases and renewals and maintenance. A software maintenance contract might be renewed on a yearly (or more) basis and might have a different Purchase Order number each time. It could have a different serial number (or even product name) so in fact, all the details may change, but the records all still need to be associated. How about adding the ability to group individual license entries under a user provided name and providing a list of those groups.... For example, I create a license group called "ArcServe" in which I can see all of my Arcserve licnes under and I can sort by date... You probably have a better idea but I hope this explains the need.
Also, we would be happy to sponsor the development of the licensing features.
+1 as well. I was adding some chargers as accessories, and was hoping to have a volts/amps/connector fields so that I could track down compatible chargers as needed.
+1 I would love to have my custom field for cable length of socket strips, network cables etc. Links to invoices on sharepoint etc.
To manage the life cycle of components e.g. hard drives I am asking for more fields. When the hard drive gets decommissioned, and it needs to be securely destroyed, the extra information is needed in the inventory database. ( if it was securely erased, when it was done, and info about physical destruction) I consider H/D as a server COMPONENT of server ASSET. (component checked out to asset) I could inventory H/D as an asset, and create extra fields for h/d model asset, but I think it would be easier to treat H/D as a component with life cycle fields. Thanks.
+1
I'm adding mobile SIM, and memory cards as phone components, and need fields for numbers, operators, storage and so on.
Also; possibly a separate discussion, but blocking names for categories that are assigned only to a single type (asset or component or ...) is cosing problems for me, since for example "cables" might be assets, components or accessories, while still getting a full listing of every cable would be helpful.
I also asked for this feature (see closed #5624). How does @snipe finance herself doing Snipe-IT, if, as she said this is "enormously complicated to implement.", maybe a donation would help (as long as a software is open source I don't have a problem donating).
+1. Would really like to have this for components. My office is paying for hosted and overall we really like the system, but trying to keep track of component details is limited without having custom fields. Ideally, we'd love to be able to have add more quantity to an existing component when we have a new order for the same component. IE, we're upgrading PCs to SSDs, and we continually by new SSDs, mostly of the same model and capacity. Rather than having a separate component entry for every single order, I'd love to have a single Component entry that increases in quantity as we order more, and lists the separate order dates.
+1 I'd love to see this on Companies and Locations. As an EPOS provider we are using Snipe-IT to record the various versions of our software amongst other things, and being able to record a Location or Company as a whole as running a particular version of our software by way of a Custom Field would be a great implementation for us.
More Options on the Costs of licenses would be nice. Example: Single costs ( for License): 100$ Maintenance costs etc. : 200 Year Yearly
Also an option that calculates the end date of the software would be nice. Now i have to put it manually everytime. A select Button thats add months/years would be nice
+1 Would love to have this. We have a lot of student users and it would be nice to include year of graduation and state identifiers as custom fields.
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!
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
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!
Maybe these requirements could be broken down again with the hope of some features being introduced?
I a really feeling the pain of not being and to handle renewals of maintained licenses well.
Please implement this! We use Dynamics and being able to track security roles, units, etc. with custom fields is absolutely vital. We are stuck with a spreadsheet until this is properly implemented.
+1 for sure!
We have many fields that are pertinent to the location that are not a part of the standard location fields. Having the ability to implement this would be a huge boon for our use.
+1 Custom Fields would be the final addition we need to fully implement Snipe-IT at my company. Especially for consumables so it is easier to track why they were used.
