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

Copy all description fields from the device / module type when creating new instance #7426

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

Originally created by @Petrapana on GitHub (Dec 26, 2022).

NetBox version

v3.3.9

Feature type

New functionality

Proposed functionality

Hi, I'd found really useful if all the description fields would copy from the device/module type while creating a new device instance / new module instance. Currently all the description fields are left blank and manual propagation of all the description fields has to be done.

Use case

I am adding the description for some ports, where they are physically located, or what is the speed of specific module. This information is later visible only on the template and not directly on the module instance itself => You have to manually navigate to different place and cannot see this info directly from the device.

Database changes

No response

External dependencies

No response

Originally created by @Petrapana on GitHub (Dec 26, 2022). ### NetBox version v3.3.9 ### Feature type New functionality ### Proposed functionality Hi, I'd found really useful if all the description fields would copy from the device/module type while creating a new device instance / new module instance. Currently all the description fields are left blank and manual propagation of all the description fields has to be done. ### Use case I am adding the description for some ports, where they are physically located, or what is the speed of specific module. This information is later visible only on the template and not directly on the module instance itself => You have to manually navigate to different place and cannot see this info directly from the device. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:23:23 +01:00
adam closed this issue 2025-12-29 20:23:23 +01:00
adam commented 2025-12-29 20:23:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 27, 2022):

NetBox intentionally does not do this because it would result in the unnecessary duplication of information. What is true regarding the characteristics of a device type (or module type) must be true for all instances of it, so replicating that information - and especially allowing it to be modified per instance - makes no sense.

Instead, the description fields on device components should contain any information relevant to that specific instance. For example, the description of an interface template might describe its physical location on the device, whereas the description on an interface might note some fault or temporary configuration pertinent to that particular interface and irrelevant to the same interface on some other instance of the device type.

This approach ensures that users can leverage both contexts of description in an efficient, consistent manner. Hope that helps!

@jeremystretch commented on GitHub (Dec 27, 2022): NetBox intentionally does not do this because it would result in the unnecessary duplication of information. What is true regarding the characteristics of a device type (or module type) must be true for all instances of it, so replicating that information - and especially allowing it to be modified per instance - makes no sense. Instead, the description fields on device components should contain any information relevant to that specific instance. For example, the description of an interface _template_ might describe its physical location on the device, whereas the description on an interface might note some fault or temporary configuration pertinent to that particular interface and irrelevant to the same interface on some other instance of the device type. This approach ensures that users can leverage both contexts of description in an efficient, consistent manner. Hope that helps!
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 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#7426
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?