Snipe-it: Feature Request: Custom Fields common to all the assets

[juanfont]

Expected Behavior (or desired behavior if a feature request)

Be able to declare custom fields that are common to all the assets (regardless of model). Or perhaps declare a Fieldset that is associated by default to all the models that are created.

---

Actual Behavior

At this moment, when you create a custom field for an asset you have to assign it to a Fieldset and then assign this Fieldset to a specific asset model. This implies that if you have a custom field that is common to all the assets (e.g. service desk ticket id, mac address...) you have to manually associate it to the all the models - and do this process every time you add a new model.

---

Thanks! :-)

Juan

[snipe]

Sorry, that’s not a duplicate. I misread.

I’m not sure which would be better here - allowing “universal” fields or default fieldsets. My worry would be that exceptions would start to pile up for “universal” fields. For example, when someone first sets up their inventory system, the field “MAC address” gets set as a universal required field.... fast forward a year, when that person has decided that they want to track office furniture as well. That could get frustrating.

I think this is a good idea, I just want to be sure we execute it in a way that won’t screw people up as the way they use Snipe-IT grows and changes over time.

[juanfont]

Thanks!!

I reckon that it is up to the user to understand that if they define a "universal" field they will find it in all the assets.

(I totally support the idea of adding MAC addresses to chairs.)

[snipe]

Its definitely up to the user, but part of our job is always to make the user experience good, and to accommodate for as many foreseeable use cases as possible. (Unlike many other open source projects, UX is pretty important to us). Many times, the feature itself isn’t that hard, but building it in a way that will make sense to the user is the challenge :)

[wilsonlspacheco]

+1

[kejones999]

Hi Folks,

I'm just in the progress of trying Snipe-IT out and had just got to the point of working out that my asset information had a "make" field that'd be nice to add universally to electronic assets but then thought I might not want to add that for all types of assets too!

How about allowing custom models to specify multiple fieldsets ? If the fieldsets are uniquely named and handled, then it should theoretically mean people can add/remove fieldsets that can be applied across multiple models without necessary being applied to all. That seems simpler to make implement in the UX front.

Regards,

Keith

[stale[bot]]

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!

[juanfont]

Noooo :(

[llecerf]

Hi,

Is this feature ever going to be implemented (either that or the solution that kejones999 proposed) ? It would be really useful for the structure i'm working on.

Cheers,

Louis

[denhyde]

Hi. I have created 12 custom fields that should be applicable to all assets without exception. E.g. default owner, funding body, account code, date disposed of, method of disposal etc. Do I manually add these 12 custom fields to every single model? Wouldn't it be easier to create a custom fieldset and add it by default to all assets or at least allow multiple custom fieldsets for each model? This functionality is really needed.

[snipe]

Do I manually add these 12 custom fields to every single model?

Yes, you can do that very easily via the Bulk Edit on Asset Models.

No, you add the custom fields to a custom fieldset, and add that to all of the models using Bulk Edit.

[llecerf]

Hi Snipe,

Do you think that it would be possible to add global custom fields or multiple fieldsets per asset model in the future ?
Thanks,
Louis

[pvnick]

In our organization we defined a "Universal Fieldset" which has custom fields that should be common to all models, and added a database trigger that automatically associates that fieldset with new models that get created without being associated with a fieldset:

/* 
    This automatically sets the fieldset to the universal fieldset on model creation, if a fieldset
    was not defined in the model definition. Allows for universal custom fields.
*/

DELIMITER ;;
CREATE TRIGGER
    set_default_fieldset
BEFORE INSERT
    ON models FOR EACH ROW IF NEW.fieldset_id is null THEN
        SET NEW.fieldset_id = (
            select id from custom_fieldsets where name = 'Universal Fieldset (do not delete)'
        );
    END IF ;;
DELIMITER ;

[lucidheart]

It's too bad this is closed and never received attention. This actually is a deal breaker for me when I was evaluating whether to use the SaaS from snipe IT. I need to add "account numbers" to make this software also work for our accounting department. It makes no sense to duplicate the efforts of tracking and the financial aspects with two different pieces of software. So I was looking to add the fields necessary for accounting to all assets.

The system is too complex to make this work for us.

[Timetrapper]

This is a feature we're looking for as well. My organization has already integrated SNIPE-IT in our logistics. But for reporting purposes all are assets fall into one of three groups. We'd like to be able to select which group a model belongs to whenever a new model is created.