starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Assign custom fields to sections #6354

New Issue
Closed
opened 2025-12-29 19:39:45 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:39:45 +01:00
Owner
Copy Link

Originally created by @KosenkoIvan on GitHub (Apr 14, 2022).

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

Originally created by @KosenkoIvan on GitHub (Apr 14, 2022). ### 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](https://user-images.githubusercontent.com/97949308/163360379-43ca88cb-8f04-40f8-a9d6-dc9c5122eb5c.png) ![image](https://user-images.githubusercontent.com/97949308/163360655-efbba70e-d82a-48a0-ba5b-1d8c0cacc760.png) ![image](https://user-images.githubusercontent.com/97949308/163360769-3ecd0bb6-99a5-4030-a985-02800ad7a7eb.png) ### 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_
adam added the type: feature label 2025-12-29 19:39:45 +01:00
adam closed this issue 2025-12-29 19:39:45 +01:00
adam commented 2025-12-29 19:39:45 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 14, 2022):

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 commented on GitHub (Apr 14, 2022): > 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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6354
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?