starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add In Ability To Export Components From Individual Devices #11355

New Issue
Closed
opened 2025-12-29 21:44:06 +01:00 by adam · 5 comments
adam commented 2025-12-29 21:44:06 +01:00
Owner
Copy Link

Originally created by @mr1716 on GitHub (Jul 8, 2025).

NetBox version

v4.3.3

Feature type

New functionality

Proposed functionality

Just like there is the ability to Create/Add New Components for each device, it would be great to be able to export those items independently as well. For example, the use case is if I want to export the interfaces for a device, I would have to go to the Intefaces tab, and then filter by that device, and then export.

This button would be able to get that done for me from the specific Device record page.

Use case

Just like there is the ability to Create/Add New Components for each device, it would be great to be able to export those items independently as well. For example, the use case is if I want to export the interfaces for a device, I would have to go to the Intefaces tab, and then filter by that device, and then export.

This button would be able to get that done for me from the specific Device record page.

Database changes

None I believe, as this is just adding a button

External dependencies

N/A

Originally created by @mr1716 on GitHub (Jul 8, 2025). ### NetBox version v4.3.3 ### Feature type New functionality ### Proposed functionality Just like there is the ability to Create/Add New Components for each device, it would be great to be able to export those items independently as well. For example, the use case is if I want to export the interfaces for a device, I would have to go to the Intefaces tab, and then filter by that device, and then export. This button would be able to get that done for me from the specific Device record page. ### Use case Just like there is the ability to Create/Add New Components for each device, it would be great to be able to export those items independently as well. For example, the use case is if I want to export the interfaces for a device, I would have to go to the Intefaces tab, and then filter by that device, and then export. This button would be able to get that done for me from the specific Device record page. ### Database changes None I believe, as this is just adding a button ### External dependencies N/A
adam added the type: featurestatus: under review labels 2025-12-29 21:44:06 +01:00
adam closed this issue 2025-12-29 21:44:06 +01:00
adam commented 2025-12-29 21:44:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 10, 2025):

While I see the argument for convenience, this is already possible by navigating to the global list for the type of component (e.g. interfaces), filtering by the desired device(s), and performing the export. Adding a dedicated export button just for components belonging to a specific device feels unintuitive IMO.

@jeremystretch commented on GitHub (Jul 10, 2025): While I see the argument for convenience, this is already possible by navigating to the global list for the type of component (e.g. interfaces), filtering by the desired device(s), and performing the export. Adding a dedicated export button just for components belonging to a specific device feels unintuitive IMO.
adam commented 2025-12-29 21:44:07 +01:00
Author
Owner
Copy Link

@mr1716 commented on GitHub (Jul 11, 2025):

@jeremystretch, in that event, then why have the ability to add those components from the Device? You could use that same argument to remove the “Add Components” button that’s already there.

I had users request this feature for the Netbox instance that we have. Didn’t take too long to implement, so figured that it’s potentially valuable to others as well

@mr1716 commented on GitHub (Jul 11, 2025): @jeremystretch, in that event, then why have the ability to add those components from the Device? You could use that same argument to remove the “Add Components” button that’s already there. I had users request this feature for the Netbox instance that we have. Didn’t take too long to implement, so figured that it’s potentially valuable to others as well
adam commented 2025-12-29 21:44:07 +01:00
Author
Owner
Copy Link

@mkarel commented on GitHub (Jul 13, 2025):

There have been time when I am doing bulk changes to say interfaces for a device, and I am in the individual device already and I just want to import/export right from that view.

@mkarel commented on GitHub (Jul 13, 2025): There have been time when I am doing bulk changes to say interfaces for a device, and I am in the individual device already and I just want to import/export right from that view.
adam commented 2025-12-29 21:44:08 +01:00
Author
Owner
Copy Link

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

then why have the ability to add those components from the Device?

That button links to a component creation form, where a specific device must be selected. The same is not true of the export list, which may have zero or more arbitrary filters applied.

@jeremystretch commented on GitHub (Jul 14, 2025): > then why have the ability to add those components from the Device? That button links to a component creation form, where a specific device _must_ be selected. The same is not true of the export list, which may have zero or more arbitrary filters applied.
adam commented 2025-12-29 21:44:08 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Jul 31, 2025):

Closing as per above comments.

@arthanson commented on GitHub (Jul 31, 2025): Closing as per above comments.
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: under review 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#11355
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?