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

Support for importing tags when importing IP addresses via CSV #4906

New Issue
Closed
opened 2025-12-29 19:22:05 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:22:05 +01:00
Owner
Copy Link

Originally created by @leethobbit on GitHub (May 14, 2021).

NetBox version

v2.11.3

Feature type

Data model extension

Proposed functionality

Currently, it is not possible to specify tags for IP addresses when importing IP addresses via CSV. It would be great if a tags column (or columns) could be implemented so tags don't require additional steps after import. The only complicating factor here is support for multiple tags at import - I'm not sure whether it is better to use multiple columns in the CSV import for tags or use some sort of delimiting character in one column. Thank you very much!

Use case

I ran into this when I decided to import all of my static IP assignments. Using tags is a great way to categorize devices - I have tags for VOIP, Radio, CCTV, HVAC, Printers, and more. This leaves room in the Description for specifying other need to know details and allows me to easily filter the view to only see one specific type of device when viewed through the IP address window. Bulk assignment of tags after import is certainly feasible for smaller deployments, but it would be great to include that in the import step since nearly all other fields are already included there.

Database changes

I'm still new to this but I don't suspect this would require DB schema changes. This should just be a matter of passing tag values from the CSV importer to the tag function or Class in Netbox.

External dependencies

No response

Originally created by @leethobbit on GitHub (May 14, 2021). ### NetBox version v2.11.3 ### Feature type Data model extension ### Proposed functionality Currently, it is not possible to specify tags for IP addresses when importing IP addresses via CSV. It would be great if a tags column (or columns) could be implemented so tags don't require additional steps after import. The only complicating factor here is support for multiple tags at import - I'm not sure whether it is better to use multiple columns in the CSV import for tags or use some sort of delimiting character in one column. Thank you very much! ### Use case I ran into this when I decided to import all of my static IP assignments. Using tags is a great way to categorize devices - I have tags for VOIP, Radio, CCTV, HVAC, Printers, and more. This leaves room in the Description for specifying other need to know details and allows me to easily filter the view to only see one specific type of device when viewed through the IP address window. Bulk assignment of tags after import is certainly feasible for smaller deployments, but it would be great to include that in the import step since nearly all other fields are already included there. ### Database changes I'm still new to this but I don't suspect this would require DB schema changes. This should just be a matter of passing tag values from the CSV importer to the tag function or Class in Netbox. ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:22:05 +01:00
adam closed this issue 2025-12-29 19:22:05 +01:00
adam commented 2025-12-29 19:22:06 +01:00
Author
Owner
Copy Link

@jaakub commented on GitHub (May 14, 2021):

Would be nice to see this extended to devices as well. We have a set of standard tags that most devices should be tagged with when created. At the moment, this is a manual/bulk step process once the devices are created.

@jaakub commented on GitHub (May 14, 2021): Would be nice to see this extended to devices as well. We have a set of standard tags that most devices should be tagged with when created. At the moment, this is a manual/bulk step process once the devices are created.
adam commented 2025-12-29 19:22:06 +01:00
Author
Owner
Copy Link

@ziggekatten commented on GitHub (May 14, 2021):

Tip. A custom script with FileVar() and you can upload files and and add whatever you like. We use that for imorting stuff that needs more than what the imports give natively.

@ziggekatten commented on GitHub (May 14, 2021): Tip. A custom script with FileVar() and you can upload files and and add whatever you like. We use that for imorting stuff that needs more than what the imports give natively.
adam commented 2025-12-29 19:22:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 18, 2021):

This should be doable by treating the tags field as its own comma-separated list of tag names encapsulated inside double quotes (CSV-in-CSV). However, the implementation will require a proper field to handle this data as well as a set of thorough tests to ensure its operation.

@jeremystretch commented on GitHub (May 18, 2021): This should be doable by treating the `tags` field as its own comma-separated list of tag names encapsulated inside double quotes (CSV-in-CSV). However, the implementation will require a proper field to handle this data as well as a set of thorough tests to ensure its operation.
adam commented 2025-12-29 19:22:06 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 18, 2021):

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. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jul 18, 2021): 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. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:22:07 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 17, 2021):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Aug 17, 2021): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: needs owner 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#4906
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?