Inheritance of asset models, or apply fieldsets to category

[sjwk]

This is effectively a duplication of #6400, but that got closed as stale some time ago with no response or activity and a subsequent comment didn't reopen it so just creating a new request for the same funtionality but with a couple of different ideas:

It would be helpful if an asset model could inherit information and settings (most specifically fieldsets) from a parent/template model. Or fieldsets applied to a category (as per #6400).

Basically any way to avoid having to go and apply the same fieldsets to every model in environments where there are a large number of models in use, assuming you want to distinguish between specific model numbers of similar machines (Dell Optiplex 7070 vs 7060 vs 7050 vs ....; all the permutations of model number of Apple Macbook 13" spanning many years etc)

Being able to just create an asset model for a 'Dell Optiplex' and then have the specific model number as an asset field rather than tied to the asset mode could work too.

This is particularly useful when importing existing data as, while the import process will create new asset models for as-yet-unseen 'make model number' combinations, it won't add the custom fieldsets to them so won't import that data. In my example above, being able to have already created a 'Dell Optiplex' asset model and have new devices that are 'Dell Optiplex' model number '7070' pick up the fieldsets or other settings from that rather than a blank asset model would surely be useful.

[happyharrysco1]

+1

[stale]

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!

[sjwk]

Still relevant.

[stale]

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!

[stale]

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!

[sjwk]

Still relevant

[stale]

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!

[stale]

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!