Include Descriptions when creating Devices from Device Type #11139

Closed
opened 2025-12-29 21:40:51 +01:00 by adam · 1 comment
Owner

Originally created by @bryanward-net on GitHub (May 7, 2025).

NetBox version

v4.2.6

Feature type

Change to existing functionality

Proposed functionality

When creating a new Device and specifying a Device Type, the new Device includes the Components (Interfaces, Console Ports, Power Ports, etc.) of the specified Device Type. However, the Description fields specified in the Components of the Device Type are not included in the new Device - they are left blank. Please copy the values of the Description fields from the Device Type's Components to the newly created Device.

Use case

The description field is useful to capture data not otherwise present in the data model, such as baud rate of console ports or pre-defined interface uses (such as ports that are dedicated for uplinks, stacking, sync of HA pairs, etc.)

Database changes

None.

External dependencies

None.

Originally created by @bryanward-net on GitHub (May 7, 2025). ### NetBox version v4.2.6 ### Feature type Change to existing functionality ### Proposed functionality When creating a new Device and specifying a Device Type, the new Device includes the Components (Interfaces, Console Ports, Power Ports, etc.) of the specified Device Type. However, the Description fields specified in the Components of the Device Type are not included in the new Device - they are left blank. Please copy the values of the Description fields from the Device Type's Components to the newly created Device. ### Use case The description field is useful to capture data not otherwise present in the data model, such as baud rate of console ports or pre-defined interface uses (such as ports that are dedicated for uplinks, stacking, sync of HA pairs, etc.) ### Database changes None. ### External dependencies None.
adam added the type: feature label 2025-12-29 21:40:51 +01:00
adam closed this issue 2025-12-29 21:40:51 +01:00
Author
Owner

@jeremystretch commented on GitHub (May 7, 2025):

This has been proposed and rejected in past issues. The description on each device component is intended to be unique; copying it from the parent device type would preclude this and result only in duplicate data.

@jeremystretch commented on GitHub (May 7, 2025): This has been proposed and rejected in past issues. The description on each device component is intended to be unique; copying it from the parent device type would preclude this and result only in duplicate data.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11139