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

Additional Custom Field Sections #3875

New Issue
Closed
opened 2025-12-29 18:31:44 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:31:44 +01:00
Owner
Copy Link

Originally created by @iunderwood on GitHub (Jul 21, 2020).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.8.8

Proposed Functionality

This proposal is to add custom fields to additional properties in Netbox, specifically rack groups.

Use Case

A building on an enterprise campus is represented by a single site. However, IDFs within that building can be represented by rack groups. Being able to add fields to rack groups can allow addition of useful information such as access method (key / card), and a facility room number, just to name a couple possibilities.

Database Changes

Unsure. This may be a simple extension of custom field functionality that is enabled for other properties.

External Dependencies

None I am aware of.

Originally created by @iunderwood on GitHub (Jul 21, 2020). ### Environment * Python version: 3.6.8 * NetBox version: 2.8.8 ### Proposed Functionality This proposal is to add custom fields to additional properties in Netbox, specifically rack groups. ### Use Case A building on an enterprise campus is represented by a single site. However, IDFs within that building can be represented by rack groups. Being able to add fields to rack groups can allow addition of useful information such as access method (key / card), and a facility room number, just to name a couple possibilities. ### Database Changes Unsure. This may be a simple extension of custom field functionality that is enabled for other properties. ### External Dependencies None I am aware of.
adam closed this issue 2025-12-29 18:31:44 +01:00
adam commented 2025-12-29 18:31:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 22, 2020):

Development of custom fields is currently frozen pending an overhaul of its current implementation; please see #4878. It's likely that support for custom fields will be expanded in the process of this work, once a solution has been agreed upon.

@jeremystretch commented on GitHub (Jul 22, 2020): Development of custom fields is currently frozen pending an overhaul of its current implementation; please see #4878. It's likely that support for custom fields will be expanded in the process of this work, once a solution has been agreed upon.
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#3875
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?