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

New Device Components Not Inheriting Description #6663

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

Originally created by @dg2assassin on GitHub (Jul 14, 2022).

NetBox version

v3.2.6

Python version

3.8

Steps to Reproduce

  1. Add a description to a component for a Device Type.
  2. Create a new Device from that Device Type
  3. Navigate to the components screen and notice no descriptions have been propagated over from the Device Type.

Device Type
Device Type

New Device
New Device

Expected Behavior

The description field set in the Device Type should propagate to the new Device instance.

Observed Behavior

It seems when the description field for components (Interfaces, Device Bays, Power Ports) are set in the "Device Type", they are not propagating to a new device during creation.

Originally created by @dg2assassin on GitHub (Jul 14, 2022). ### NetBox version v3.2.6 ### Python version 3.8 ### Steps to Reproduce 1. Add a description to a component for a Device Type. 3. Create a new Device from that Device Type 4. Navigate to the components screen and notice no descriptions have been propagated over from the Device Type. Device Type ![Device Type](https://user-images.githubusercontent.com/25205963/179076272-763bc9e0-913c-4ce4-87be-23afd0c59f84.PNG) New Device ![New Device](https://user-images.githubusercontent.com/25205963/179076328-bba87340-08e2-4a1e-ad32-cfe3e081af16.PNG) ### Expected Behavior The description field set in the Device Type should propagate to the new Device instance. ### Observed Behavior It seems when the description field for components (Interfaces, Device Bays, Power Ports) are set in the "Device Type", they are not propagating to a new device during creation.
adam added the status: duplicate label 2025-12-29 19:43:38 +01:00
adam closed this issue 2025-12-29 19:43:38 +01:00
adam commented 2025-12-29 19:43:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 14, 2022):

This is intended behavior and has been discussed previously. Please search closed issues before submitting a new one.

@jeremystretch commented on GitHub (Jul 14, 2022): This is intended behavior and has been discussed previously. Please search closed issues before submitting a new one.
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
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#6663
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?