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

Add custom fields to templates #9183

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

Originally created by @llamafilm on GitHub (Feb 2, 2024).

NetBox version

v3.7.0

Feature type

Data model extension

Proposed functionality

I’d like to enter custom fields on a Device Type (template). When instantiating a new Device, it will copy custom field values from the template. After that, the fields can be customized on each device, just like any other field.

The same thing would apply to all other types of templates, like Power Outlets, etc.

Use case

I use a multi-select custom field on all Devices called telegraf_config that defines which Telegraf input template should be used to monitor its health. This field is usually the same for all devices of a given type.

Another use case, described in #14971: I would add a Boolean field to each power outlet to indicate whether it’s controllable.

Another use case: a custom field called uri_handler with values such as http, ssh, vnc,rdp. I would use this field in custom links like this: {{object.cf.uri_handler}}://{{object.primary_ip} to make it easy to connect to each device’s management interface.

Database changes

I suppose it would need a new field on each template.

External dependencies

None

Originally created by @llamafilm on GitHub (Feb 2, 2024). ### NetBox version v3.7.0 ### Feature type Data model extension ### Proposed functionality I’d like to enter custom fields on a Device Type (template). When instantiating a new Device, it will copy custom field values from the template. After that, the fields can be customized on each device, just like any other field. The same thing would apply to all other types of templates, like Power Outlets, etc. ### Use case I use a multi-select custom field on all Devices called `telegraf_config` that defines which Telegraf input template should be used to monitor its health. This field is usually the same for all devices of a given type. Another use case, described in #14971: I would add a Boolean field to each power outlet to indicate whether it’s controllable. Another use case: a custom field called `uri_handler` with values such as http, ssh, vnc,rdp. I would use this field in custom links like this: `{{object.cf.uri_handler}}://{{object.primary_ip}` to make it easy to connect to each device’s management interface. ### Database changes I suppose it would need a new field on each template. ### External dependencies None
adam added the type: featurestatus: duplicate labels 2025-12-29 20:46:42 +01:00
adam closed this issue 2025-12-29 20:46:42 +01:00
adam commented 2025-12-29 20:46:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 2, 2024):

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #9243 for further discussion.

@jeremystretch commented on GitHub (Feb 2, 2024): Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #9243 for further discussion.
adam commented 2025-12-29 20:46:44 +01:00
Author
Owner
Copy Link

@llamafilm commented on GitHub (Feb 2, 2024):

Thanks, I hadn’t seen the other issue. That one is closed and locked so further discussion is not possible. It looks like several users have requested this feature, and nobody raised any counter argument. So why close the discussion?

@llamafilm commented on GitHub (Feb 2, 2024): Thanks, I hadn’t seen the other issue. That one is closed and locked so further discussion is not possible. It looks like several users have requested this feature, and nobody raised any counter argument. So why close the discussion?
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: duplicate 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#9183
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?