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

Allow specifying Component on Inventory Item import #6441

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

Originally created by @sleepinggenius2 on GitHub (May 3, 2022).

Originally assigned to: @kkthxbye-code on GitHub.

NetBox version

v3.2.2

Feature type

Change to existing functionality

Proposed functionality

The work that was done in #7846 is really useful for tracking things like SFPs that cannot currently be modeled as modules due to lack of module nesting. Unfortunately, there does not appear to be a way to assign inventory items to components in bulk. I would propose adding something like component and component_type fields to the Inventory Item import form in order to facilitate this function.

Use case

Populating inventory items for components one at a time is tedious and time-consuming. It would be nice to be able to use the existing bulk import functionality to make this task easier.

Database changes

None

External dependencies

None

Originally created by @sleepinggenius2 on GitHub (May 3, 2022). Originally assigned to: @kkthxbye-code on GitHub. ### NetBox version v3.2.2 ### Feature type Change to existing functionality ### Proposed functionality The work that was done in #7846 is really useful for tracking things like SFPs that cannot currently be modeled as modules due to lack of module nesting. Unfortunately, there does not appear to be a way to assign inventory items to components in bulk. I would propose adding something like *component* and *component_type* fields to the *Inventory Item* import form in order to facilitate this function. ### Use case Populating inventory items for components one at a time is tedious and time-consuming. It would be nice to be able to use the existing bulk import functionality to make this task easier. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 19:40:46 +01:00
adam closed this issue 2025-12-29 19:40:46 +01:00
adam commented 2025-12-29 19:40:46 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 3, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jul 3, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
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: accepted 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#6441
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?