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!](https://www.bountysource.com/issues/50497931-custom-fields-for-non-assets-licenses-accessories-consumables-components-users?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).

[hyggja]

+1

[andro44]

+1

[Relix360]

+1

[yosiasz]

what would it take to make this happen? bounty?

[snipe]

@yosiasz It would require a huge rewrite, and I'm not even sure we'd take a PR for it since it touches so many things. It's in the works. Please just remain patient.

[viclou]

+1 FD 19378

[sowi-it]

+1

[winstan]

Looking forward to this. Intend to track multiple network interfaces (with extended details) per asset. :)

[MrCaspan]

I would love to donate to the cause also Snipe if that helps with getting the ball rolling after v5 is out!

I know this is a no no but for now we will never use the 'Licensed to Email' or 'Licensed to Name' field in the Software form, I just renamed the language value for it in the language file (snipe-it/resources/lang/en/admin/licenses/form.php) to the field name I wanted. I have to redo this change after each update but if you only need one or two fields for now is a nice simple easy stop gap. For us we need just an single Media ID field that tell us where the Media is located on our filling system for this software.

Also just an idea and maybe temporarily Snipe could use some JavaScript and pull JSON data from the notes field and dynamically show it on the table view? Just an idea

[kirillk77]

+1

[crax0]

+1

[alainseys]

+1

[avigi25]

+1

[SufiSR]

+1 Custom Fields for Licenses I had this wonderful idea of tracking GDPR compliance for software licenses / products where i would have custom fields for the GDPR policy review data, data residency and to what extend a user may use the software in terms of PII - which I would then inform them about in the checkout email.

Too bad it's not there yet.

[snipe]

Too bad indeed.

[MrCaspan]

@snipe Just lock this thread. You have told us it's coming but people want to still throw the team shade and constantly saying +1 You have better things to do then to listen to the same story over and over.

[acerspyro]

@MrCaspan I'm a bit disillusioned with SnipeIt at this point. I thought them incorporating into a company that funds itself off of providing support would allow them to make development faster, but most of what they do right now seems to be code maintenance rather than development.

The fact remains that they are still the best open-source asset tracker out there, but sometimes being the best in a category just isn't enough when crucial features are missing and lots of issues remain unsolved. Our company is now at the point where we're looking for alternatives as we've just hit too many limitations and had too many issues with the software.

[MrCaspan]

This is an issue tracing system. The issue has been described and the team has replied it's in the works but it's going to take a lot to do! Emotions are now in play and people feel frustrated understandably but. It's free software. If it does not suit your needs and the development cycle is not fast enough then you only have one choice. Being frustrated at the developers won't do a thing but make them feel like why bother even trying, they have said it requires a full rewrite to do this. If you can't wait and you have to have these features then you have to do what you have to do. They have a very thankless job and are always expected to produce! I get people's frustration but let's give them some breathing room and some encouragement!!

[acerspyro]

This is an issue tracing system. The issue has been described and the team has replied it's in the works but it's going to take a lot to do! Emotions are now in play and people feel frustrated understandably but. It's free software. If it does not suit your needs and the development cycle is not fast enough then you only have one choice. Being frustrated at the developers won't do a thing but make them feel like why bother even trying, they have said it requires a full rewrite to do this. If you can't wait and you have to have these features then you have to do what you have to do. They have a very thankless job and are always expected to produce! I get people's frustration but let's give them some breathing room and some encouragement!!

I'm not throwing shade at the team, I'm simply stating that even though the team is receiving funding through paid support and hosting, the development is stuck in a maintenance cycle with little improvements.

It's important, even as an open-source developer, to hear out your users and understand how they feel about the software you're building so you don't just end up going in a random direction and stay on track with the needs of the users. Issue trackers are as much about bug reports and feature requests as they are about discussions regarding the project itself.

I'm glad people were able to take personal time out of their own day to come together and build this software. It's served us well, I simply believe our company has hit its limitations and outgrown it.

If the team has no desire to work on this feature, they should lock and close the thread.

Otherwise, it should stay open, and I recommend that people instead voice their support using a 👍 reaction on the original request so as not to spam the conversation.

[snipe]

@acerspyro You can throw all the shade you like, it won’t change the fact that there’s a lot going on behind the scenes, including the planned release of v6 in September. The feature is being worked on actively, but we are a small team. V6 required an entire framework upgrade and is being worked on every day, and custom fields have always been a hard problem to solve correctly. (Easy to solve, not easy to solve correctly. There are speed implications, database limitations, UX and UI implications, and so on - not to mention the dozen other features we’re trying to put into v6.)

If you need to move to another solution, be my guest, but please don’t lecture me on how to run an open source project or my company.

[snipe]

@MrCaspan thank you for your patience and understanding. This is still very much a top priority for the next major release. ❤️

[rhelbling22]

Following

[rhelbling22]

Adding custom fields and fieldsets to Accessories, Consumables and Components is definitely a need. Do you have any sort of an ETA on this feature, please? Thanks.

[clintseban]

@snipe Any progress on this requirement? Many of them are eagerly waiting to get an answer from the Snipe-IT team.

[yechunshen]

already done?

[ryanmerolle]

already done?

Not sure what you are talking about. The issue is still open. If it’s a sarcastic comment, @snipe and team do an amazing job and it will come when it comes.

[snipe]

It's still on the short term roadmap, but it affects a LOT of moving parts, and we have to be careful when we make such sweeping changes. There are always unintended consequences.

[nghia-dang]

From what I could tell, people had asked for custom fields that can be added to people, but does this include a custom field added to an asset, whereby you can select via a picker to assign a person to the custom field within the asset?

Eg. If I had a 'Purchaser' custom field on an asset that I could choose a person from (and if I visited the person details I'd see the assets assigned via this field)

[Noofayroz]

is it already there ?

[jbryant88]

Im just wondering if the Custom Fields for Licenses is something that is coming? OR if its possible to add to the Purchase costs to have a separate entry for the Total cost of the Licenses (Ie Office with 100 seats) and separate the per seat cost that posts to the People

[daliborpuljiz]

I've come here just to find out the custom fields are not ready for non-assets. Looking forward to it, as well :)

[rmscode]

Bump...PLEASE. Custom fields for all categories.

[ZebboKlaufix]

This would be a great thing to have. Please allow custom fields for categories.

[PhantomPhreak]

This feature was also requested here in 2016: https://github.com/snipe/snipe-it/issues/2934 That thread contain a lot of interesting details, as well as signs of how violent the repository owner’s reaction was to users’ attempts to explain how important this feature is to them. And after 7 years, nothing has changed. I wish everyone waiting for this feature strong patience.

[SufiSR]

With all due respect - I am not sure how this last post is any helpful. First and foremost, it’s an open source project and actually a very good one - and I would think that might be due to the repository owner.

[kgortmak]

Agreed. Read the whole long discussion, and it has nothing to do wit the request here. Basic problem there is that the dev's should not have used the fieldname 'serial number' in the components data set. In stead they shoud have used 'part number', as that would identify a specific part (or series of parts with the same part number) Calling it Serial number (which basically is a unique identity number) causes people to create expectations that are not correct. Other thing in that discussion is the fact a lot of people completely ignore the fact that you can check out assets to another assets. Or create a specific category. There where people calling switches components. In my book, switches are assets in the Network Infrastructure category. You can use custom fields to register stack position or something.

Nevertheless, these kind of feature requests are not "must have's" according to the dev's, which is a pitty, since so many people acknowledged the need for it. ;-)

[iamsumesh]

+1.

[MrCaspan]

I think it's time to lock the thread. No one knows how to read

[heikoboehme]

just as an idea: have a look at the custom field / value function as implemented in redmine ( redmine.org) . it works incredibly well. custom fields have been implemented for all the different documentation objects in a very simple way

[rmscode]

I think it's time to lock the thread. No one knows how to read

What exactly are we missing?

[SufiSR]

I think it's time to lock the thread. No one knows how to read

What exactly are we missing?

Nothing really - the other guy seems to be misreading the duplicate ;)

[MrCaspan]

Sorry I think 2 different issues have been merged and the huge thread is gone. You can follow an issue without pinging the entire community to follow this issues. It's annoying to get a "me too ping" every week. This was in the old thread to just subscribe if you want updates.. the +1 comments were just annoying and not helpful. The dev knows it's an issue and have said it's a full rewrite to do it so maybe happening but maybe not because it's huge!! Subscribe to the issue and wait patiently or pitch in to help with the project. No more +1's please or only post if you have info about it.. That was the summary of the old discussion about this. Just my 2 cents take it for what it is..

[rmscode]

It's annoying to get a "me too ping" every week.

Fair point.

I haven't spent a great amount of time reading through all the related issues, but what I got out of it is that Snipe doesn't seem all that interested considering the fact that there are "hundreds" of other features requests on the to-do list, allegedly. I recall reading one of her direct replies to someone being a bit snarky . . . "I welcome your pull request". Snipe's most recent solution is almost as if she's saying "deal with it". I could be reading her tone completely wrong.

I guess I'll just patiently wait and remain hopeful.

[JCollinsMPS]

I, too, look forward to expanded functionality. We need to add employee keycards into our system and would like to do so as accessories. However, there is no good way to display the "token #" on the keycard in Snipe. Using the notes section when checking it out to a user only shows that information in the history of the accessory, not the user. We will probably just make it an accessory at this point so we can track things in Snipe.

[rthreis404]

Hello Everyone, I'm very interested in this feature too. I'd like to be able to define things like :

Assets:

• Laptops
• Desktop
• ... Accessories:
• Keyboard
• Headset
• Mouse
• Docking station

Custom Fields

• Connection : wired || wireless
• Layout : AZERTY (BE) || AZERTY (FR) || QWERTZ (DE) || QWERTY (UK)
• Power : 60W || 120W || 180W ||

Be able to: Layout used with: Asset>Laptops && Accessories>Keyboard Connection used with: Accessories>Keyboard && Headset && Mouse Power used with: Accessories>Docking station

I'm not sure if this is clear, and I don't know how the database tables are linked together in order to set this up. I would also like to thank you for the great work you're doing on this. Have a great day all,

[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."