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

Customization features added #7956

New Issue
Closed
opened 2025-12-29 20:30:28 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:30:28 +01:00
Owner
Copy Link

Originally created by @Bluecatzmv on GitHub (Apr 28, 2023).

NetBox version

v3.1.7

Feature type

Change to existing functionality

Proposed functionality

The existing user customization feature is not flexible enough, the custom fields are not retrievable by the system, they are simply fields, and there is no option to set the custom fields as new information that can be jumped to edit. The custom link option does not point to a small enough scope of the directory, it will display all the sub items under the major category of the directory, the user cannot choose to have the custom link display in the smallest category of the individual information pages.

Use case

For example, after creating a server device, adding device properties to it, where information such as hard disk, memory stick, CPU, network card, etc. can only be added by customization, but the custom fields cannot be retrieved by the system, and the custom fields are simply in the form of strings, and cannot be bound to the device, or jumped by clicking on the custom fields in the device interface, because currently it is not possible to bind and jump between the device and the device, while for devices such as servers, the existing information options cannot meet the demand, and a lot of information needs to be added by customization.

The flexibility of custom links is also not enough, and the subdivision of the specified type is not fine enough, if it can be subdivided into each minimum page, it will greatly improve the experience of using.

Database changes

No response

External dependencies

No response

Originally created by @Bluecatzmv on GitHub (Apr 28, 2023). ### NetBox version v3.1.7 ### Feature type Change to existing functionality ### Proposed functionality The existing user customization feature is not flexible enough, the custom fields are not retrievable by the system, they are simply fields, and there is no option to set the custom fields as new information that can be jumped to edit. The custom link option does not point to a small enough scope of the directory, it will display all the sub items under the major category of the directory, the user cannot choose to have the custom link display in the smallest category of the individual information pages. ### Use case For example, after creating a server device, adding device properties to it, where information such as hard disk, memory stick, CPU, network card, etc. can only be added by customization, but the custom fields cannot be retrieved by the system, and the custom fields are simply in the form of strings, and cannot be bound to the device, or jumped by clicking on the custom fields in the device interface, because currently it is not possible to bind and jump between the device and the device, while for devices such as servers, the existing information options cannot meet the demand, and a lot of information needs to be added by customization. The flexibility of custom links is also not enough, and the subdivision of the specified type is not fine enough, if it can be subdivided into each minimum page, it will greatly improve the experience of using. ### Database changes _No response_ ### External dependencies _No response_
adam closed this issue 2025-12-29 20:30:28 +01:00
adam commented 2025-12-29 20:30:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 28, 2023):

Converting this to a discussion as it's not clear what, if any, changes are actually being proposed.

@jeremystretch commented on GitHub (Apr 28, 2023): Converting this to a discussion as it's not clear what, if any, changes are actually being proposed.
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
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#7956
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?