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

Feature request: Adding custom fields to device roles #1991

New Issue
Closed
opened 2025-12-29 17:21:14 +01:00 by adam · 3 comments
adam commented 2025-12-29 17:21:14 +01:00
Owner
Copy Link

Originally created by @mxxxc on GitHub (Sep 6, 2018).

Environment

  • Python version: 3.4
  • NetBox version: 2.4.4

Proposed Functionality

Allowing the addition of custom fields to device role objects.

Use Case

We'd like to provision different devices automatically (OS, configuration) according to their role in NetBox, through external automated systems that can hook into the API and web hooks. In order to to do that we need to store the ID mapping from roles to those external systems' databases, so they can be looked up from the single source of truth by the tooling we use. :)

This seems very synonymous with the example named in the documentation, which is also an external system ID associated with the entity. As such it seems like a natural fit for NetBox integration.

Database Changes

N/A

External Dependencies

N/A

Originally created by @mxxxc on GitHub (Sep 6, 2018). ### Environment * Python version: 3.4 * NetBox version: 2.4.4 ### Proposed Functionality Allowing the addition of custom fields to device role objects. ### Use Case We'd like to provision different devices automatically (OS, configuration) according to their role in NetBox, through external automated systems that can hook into the API and web hooks. In order to to do that we need to store the ID mapping from roles to those external systems' databases, so they can be looked up from the single source of truth by the tooling we use. :) This seems very synonymous with the example named in [the documentation](https://netbox.readthedocs.io/en/latest/additional-features/custom-fields/), which is also an external system ID associated with the entity. As such it seems like a natural fit for NetBox integration. ### Database Changes N/A ### External Dependencies N/A
adam closed this issue 2025-12-29 17:21:14 +01:00
adam commented 2025-12-29 17:21:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 13, 2018):

Thank you for your interest in NetBox. We require that all issues be submitted using one of the templates provided here. This is to ensure that only valid issues are reported and that each issue includes all the information necessary for a developer to act on it. Please update your issue so that it matches the appropriate template (this may require rewriting your issue entirely). This issue will be closed in one week if it has not been updated. Thanks!

@jeremystretch commented on GitHub (Sep 13, 2018): Thank you for your interest in NetBox. We require that all issues be submitted using one of the templates provided [here](https://github.com/digitalocean/netbox/tree/develop/.github/ISSUE_TEMPLATE). This is to ensure that only valid issues are reported and that each issue includes all the information necessary for a developer to act on it. Please update your issue so that it matches the appropriate template (this may require rewriting your issue entirely). This issue will be closed in one week if it has not been updated. Thanks!
adam commented 2025-12-29 17:21:16 +01:00
Author
Owner
Copy Link

@mxxxc commented on GitHub (Sep 13, 2018):

Ah, apologies! The issue text has been updated.

@mxxxc commented on GitHub (Sep 13, 2018): Ah, apologies! The issue text has been updated.
adam commented 2025-12-29 17:21:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 13, 2018):

Per the FAQ we are not adding custom fields to any additional models at this time.

@jeremystretch commented on GitHub (Sep 13, 2018): Per the [FAQ](https://github.com/digitalocean/netbox/wiki/Frequently-Asked-Questions#can-we-add-custom-fields-to-more-models) we are not adding custom fields to any additional models at this time.
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#1991
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?