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

Device components: Extend filter criteria by "device type" #6930

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

Originally created by @Daniel841511 on GitHub (Sep 2, 2022).

NetBox version

v3.2.2

Feature type

New functionality

Proposed functionality

Currently device components like interfaces, ports or module bays can be filtered in device section by region, site group, site, location, virtual chassis and device. I would propose to add "device type". This can be helpful updating components from multiple existing devices.

Use case

If there is a mistake in the modelling of a device type (e.g. wrong interface type or missing labels on components) and the components needs to be updated, deleted and recreated.
This applies mainly to the situation when you must not delete existing devices from that type (e.g since devices are already transfered to other IT systems with its parameters).
By filtering device compoentes (like interfaces) by device type you could easily delete them and insert new ones by CSV import fuction.

Database changes

no changes to db

External dependencies

no dependencies

Originally created by @Daniel841511 on GitHub (Sep 2, 2022). ### NetBox version v3.2.2 ### Feature type New functionality ### Proposed functionality Currently device components like interfaces, ports or module bays can be filtered in device section by region, site group, site, location, virtual chassis and device. I would propose to add "device type". This can be helpful updating components from multiple existing devices. ### Use case If there is a mistake in the modelling of a device type (e.g. wrong interface type or missing labels on components) and the components needs to be updated, deleted and recreated. This applies mainly to the situation when you must not delete existing devices from that type (e.g since devices are already transfered to other IT systems with its parameters). By filtering device compoentes (like interfaces) by device type you could easily delete them and insert new ones by CSV import fuction. ### Database changes no changes to db ### External dependencies no dependencies
adam added the type: feature label 2025-12-29 19:46:54 +01:00
adam closed this issue 2025-12-29 19:46:54 +01:00
adam commented 2025-12-29 19:46:54 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 6, 2022):

There is no relationship from an instantiated component (such as an interface) to the device type from which it was originally defined (if there even was one), so I don't think what you're describing is feasible.

If there is a mistake in the modelling of a device type (e.g. wrong interface type or missing labels on components) and the components needs to be updated, deleted and recreated.

You can easily write a report to perform this validation across all devices if needed.

@jeremystretch commented on GitHub (Sep 6, 2022): There is no relationship from an instantiated component (such as an interface) to the device type from which it was originally defined (if there even was one), so I don't think what you're describing is feasible. > If there is a mistake in the modelling of a device type (e.g. wrong interface type or missing labels on components) and the components needs to be updated, deleted and recreated. You can easily write a [report](https://docs.netbox.dev/en/stable/customization/reports/) to perform this validation across all devices if needed.
adam commented 2025-12-29 19:46:54 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 15, 2022):

I'm going to close this as the proposed functionality doesn't seem feasible, and there are other potential solutions available. However you're welcome to ask that this be re-opened if you would like to draft a specific implementation that you believe would deliver the prescribed functionality.

@jeremystretch commented on GitHub (Sep 15, 2022): I'm going to close this as the proposed functionality doesn't seem feasible, and there are other potential solutions available. However you're welcome to ask that this be re-opened if you would like to draft a specific implementation that you believe would deliver the prescribed functionality.
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#6930
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?