Custom Fields for Non-Assets (Licenses, Accessories, Consumables, Components, Users, Models, etc)

[snipe]

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.

[sjlaird]

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.

[kagashe]

+1 for this would be great to have.

[tbradsha]

+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.

[Puddl36lum]

Any update on when these changes might get rolled out?

[snipe]

Not any time soon. It's enormously complicated to implement.

[LawrenceIRL]

+1 I would also be very interested in this.

[neironus]

+1! Custom fields for components a very important feature.

[troubblegum]

+1 I would love to have my custom field for cable length of socket strips, network cables etc. Links to invoices on sharepoint etc.

[invuser]

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.

[patricmutwiri]

I'd love to have custom fields for non-assets also.

[harcesz]

+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.

[00shorty]

We're also interested in this feature.

[mai-wand]

Custom fields for accessories would be great and very necessary.

@snipe is there a roadmap?

[koyuncuoglugithub]

up

[kekec777]

Sign me up ! :)

[rmscode]

Custom fields for accessories would be great and very necessary.

@snipe is there a roadmap?

I don't believe it's on any "roadmap". I do recall her replying to a user once with, "I welcome your pull request" . . . as if to say "If you want this feature, contribute to the project and add it yourself."

[gertz22]

UP
I'm also interested in this feature mainly licences.

[turist79]

I don`t think this will be ever implemented considering for how long the issue is being discussed.
The lack of custom fileds in components and inability to assign multiple fieldsets to one asset (component) are showstoppers for us unfortunately.
I wish there existed blend between SnipeIt and Openboxes/PartKeepr... :)

[snipe]

I don`t think this will be ever implemented considering for how long the issue is being discussed.

@turist79 - appreciate your unsolicited opinion, but that's simply not true. It's a massive change, and we have to be careful. There's already a PR open for adding custom fields to users, but we have to wait for v7 to be released before we can move forward on that.

[turist79]

I don`t think this will be ever implemented considering for how long the issue is being discussed.

@turist79 - appreciate your unsolicited opinion, but that's simply not true. It's a massive change, and we have to be careful. There's already a PR open for adding custom fields to users, but we have to wait for v7 to be released before we can move forward on that.

Happy to hear that there is some progress in that regard.
Probably the issue here could be lack of feedback to the community since the feature is so long-awaited by many.
PS: in my opinion the best solution for those who miss this feature would be to use assets instead of components, the possibility to "link" assets to assets will create same kind of relationship actually but with added benefits of custom fields.

[snipe]

Probably the issue here could be lack of feedback to the community since the feature is so long-awaited by many.

The ticket itself shows multiple updates in the way of linked issues. There just isn't that much tangible to report right now, as the underpinnings need to be updated to v7, and then the new branch needs to be tested on v7, but the UI updates that this would require (and 100 other things) are dependent the v7 release, as we've mentioned in those linked tickets, on our blog, in our Discord, and every other place imaginable.

PS: in my opinion the best solution for those who miss this feature would be to use assets instead of components,

This is literally what we always recommend.

the possibility to "link" assets to assets

You can already assign assets to other assets.

[mauro-miatello]

the possibility to "link" assets to assets will create same kind of relationship actually but with added benefits of custom fields.

#14537

[PietSkietVerniet]

I'm very keen on seeing a feature that lets me add custom fields to user accounts ("people") in Snipe-IT.
Right now, I'm adding a tag in the Notes section which i can query from the database directly to do a report on.

[jay-chuang]

When these request will be added into Snipe-it system?

[huifei0129]

I'd love to have custom fields for non-assets also.
Hope it can be done

[shanemartin22]

+1 for custom fields in Locations and People.
Now that v7 is out, any expected timeframe for this?

[snipe]

There is a WIP PR already open for custom fields on users.

[deeepakkumarthakur16]

Much awaited feature.

[ZapodD]

Any news, any progress information?

[denladdi]

very interested in this feature too!

[jLebioda]

+1

[phgravel]

Also interested!

[Mike-NP]

+1

[laserlars3000]

+1, in combination with fieldsets would be great