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

Enable custom fields for organizational models #4295

New Issue
Closed
opened 2025-12-29 18:34:29 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:34:29 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Nov 23, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6.9
  • NetBox version: 2.9.9

Proposed Functionality

Enable support for custom fields on organizational models (e.g. circuit types, rack roles, device roles, VLAN groups, etc.).

Use Case

Extension of NetBox's custom fields feature has long been demanded by users. Now that custom fields has been reimplemented in a sufficiently performant manner, we can revisit this.

Database Changes

Add a custom_field_data to each applicable model (via subclassing CustomFieldModel).

External Dependencies

None

Originally created by @jeremystretch on GitHub (Nov 23, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.6.9 * NetBox version: 2.9.9 ### Proposed Functionality Enable support for custom fields on organizational models (e.g. circuit types, rack roles, device roles, VLAN groups, etc.). ### Use Case Extension of NetBox's custom fields feature has long been demanded by users. Now that custom fields has been reimplemented in a sufficiently performant manner, we can revisit this. ### Database Changes Add a `custom_field_data` to each applicable model (via subclassing CustomFieldModel). ### External Dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 18:34:29 +01:00
adam closed this issue 2025-12-29 18:34:29 +01:00
adam commented 2025-12-29 18:34:29 +01:00
Author
Owner
Copy Link

@mngan commented on GitHub (Dec 1, 2020):

Can I add a vote for custom fields of Interfaces too?

@mngan commented on GitHub (Dec 1, 2020): Can I add a vote for custom fields of `Interfaces` too?
adam commented 2025-12-29 18:34:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 1, 2020):

@mngan No, that is beyond the scope of this issue. (Edit: See #5401)

@jeremystretch commented on GitHub (Dec 1, 2020): @mngan No, that is beyond the scope of this issue. (Edit: See #5401)
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 status: accepted 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#4295
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?