[Feature Request]: categories, custom fields

[serkanyardim]

Is your feature request related to a problem? Please describe.

Hi sir,

1. Custom fields: and then there are the field sets. And these field sets are also transferred to the model.

But essentially the field set should be assigned to the category, not the model. For example, there is the switch category. And we made a field: the number of ports. It's hp procurve, brocade, cisco 2900, it's wrong to transfer to individual models like this. Instead, the field must be assigned to the switch category.

2. There should also be custom areas that appeal to the general public. For example, I have a field called "Group" and I want to assign this field to all. Or any other field but it will be assigned to all categories.

Let's combine the 1st and 2nd items:

Fields of a category: basic fields + public custom fields + category specific custom fields will be shaped.

In this way, a building becomes healthier.

3.: Categories must have subcategories, you can limit this to a maximum of 3 levels.

Describe the solution you'd like

The solution also provided.

Describe alternatives you've considered

No response

Additional context

No response

[snipe]

But essentially the field set should be assigned to the category, not the model.

Unfortunately, this just isn't true for everyone, and would be a pretty big change in a lot of people's workflows. Certain models will have things that other models in their category (Dell service tags, for example) just won't have.

There should also be custom areas that appeal to the general public. For example, I have a field called "Group" and I want to assign this field to all.

I'm not sure what you mean here. This is a custom field called group? You can assign it to all using the "Add this to all fieldsets" option.

Categories must have subcategories, you can limit this to a maximum of 3 levels.

That's not currently a high priority, as nesting creates recursion and that can be challenging to handle. Normally People just use the test as an implied nesting, such as "General", "General > Network" and then "General > Network > Switches". It might be something we look at for version 7, but it wouldn't happen before then - and I'm still not really on board with custom fields on categories. While it makes sense in some scenarios, it doesn't make sense for all, and it's very easy to add fields to fieldsets in bulk.

I think the interruption in existing users' workflows makes that one a non-starter for me.