Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow specifying Component on Inventory Item import #9285

Closed
sleepinggenius2 opened this issue May 3, 2022 · 1 comment · Fixed by #11275
Closed

Allow specifying Component on Inventory Item import #9285

sleepinggenius2 opened this issue May 3, 2022 · 1 comment · Fixed by #11275
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@sleepinggenius2
Copy link
Contributor

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

@sleepinggenius2 sleepinggenius2 added the type: feature Introduction of new functionality to the application label May 3, 2022
@github-actions
Copy link
Contributor

github-actions bot commented 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 github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Jul 3, 2022
@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed pending closure Requires immediate attention to avoid being closed for inactivity labels Jul 27, 2022
@arthanson arthanson self-assigned this Sep 2, 2022
@arthanson arthanson added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Sep 2, 2022
@arthanson arthanson removed their assignment Oct 12, 2022
@arthanson arthanson added the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Oct 12, 2022
@kkthxbye-code kkthxbye-code self-assigned this Dec 21, 2022
@kkthxbye-code kkthxbye-code removed the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Dec 21, 2022
jeremystretch added a commit that referenced this issue Dec 22, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants