Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assign custom fields to sections #9126

Closed
KosenkoIvan opened this issue Apr 14, 2022 · 1 comment
Closed

Assign custom fields to sections #9126

KosenkoIvan opened this issue Apr 14, 2022 · 1 comment
Labels
type: feature Introduction of new functionality to the application

Comments

@KosenkoIvan
Copy link

NetBox version

nexbox (v3.1.5)

Feature type

Change to existing functionality

Proposed functionality

It would be convenient to choose where to place custom fields. Not all information in the Custom fields section should be located there. We suggest creating a choice of placing a custom field, for example, in the device, management or other sector. We are faced with the problem of finding a custom field. We need to look for many unique data in custom fields, for this we use a filter every time, which slows down the process of work. Search without a filter does not find a custom field.
image
image
image

Use case

We see such solutions to this problem.
1.Custom fields are moved to sections and thus the search finds them without a filter.
2.Custom fields are included in the search without a filter.

This will speed up the search time and make it easier to navigate.

Database changes

No response

External dependencies

No response

@KosenkoIvan KosenkoIvan added the type: feature Introduction of new functionality to the application label Apr 14, 2022
@jeremystretch
Copy link
Member

Not all information in the Custom fields section should be located there.

Custom fields are intentionally called out and organized separately to avoid confusion with built-in fields.

We suggest creating a choice of placing a custom field, for example, in the device, management or other sector.

Not only is this technically infeasible, it would be very difficult to accommodate from a UI design perspective. We're going to keep custom fields in their own section, but you may be interested in #8495, which seeks to provide better control over how the fields are grouped within that section.

@jeremystretch jeremystretch closed this as not planned Won't fix, can't repro, duplicate, stale Apr 14, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants