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

Copy tags from Device-Type when creating new device #8393

New Issue
Closed
opened 2025-12-29 20:36:09 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:36:09 +01:00
Owner
Copy Link

Originally created by @ekrichbaum on GitHub (Jul 31, 2023).

NetBox version

v3.5.7

Feature type

Change to existing functionality

Proposed functionality

Copy any tags applied to the device-type to a newly created device of that type.

Use case

With bulk edit, we can easily add a tag to existing items. Creating a new device of a specific type would not need an edit if the tags propagated to the device.

A tag, such as "End of Sale - Nov 2023", can be then applied to any devices created as they come into the warehouse and will be visible on a list without further edits. Our warehouse doesn't have any information about EOS/EOL etc. and doesn't handle the ordering, just the addition to inventory.

Database changes

None

External dependencies

None

Originally created by @ekrichbaum on GitHub (Jul 31, 2023). ### NetBox version v3.5.7 ### Feature type Change to existing functionality ### Proposed functionality Copy any tags applied to the device-type to a newly created device of that type. ### Use case With bulk edit, we can easily add a tag to existing items. Creating a new device of a specific type would not need an edit if the tags propagated to the device. A tag, such as "End of Sale - Nov 2023", can be then applied to any devices created as they come into the warehouse and will be visible on a list without further edits. Our warehouse doesn't have any information about EOS/EOL etc. and doesn't handle the ordering, just the addition to inventory. ### Database changes None ### External dependencies None
adam added the type: feature label 2025-12-29 20:36:09 +01:00
adam closed this issue 2025-12-29 20:36:09 +01:00
adam commented 2025-12-29 20:36:09 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Jul 31, 2023):

My personal opinion is that this isn't a great idea. We use tags on device types and we use tags on devices, and they can differ. Tags on devicetypes apply to all the devices of that devicetype, while individual devices of that devicetype can have different tags based on different characteristics.

If we were to do this, I think we should retain the current functionality, but provide a new field with "Replicated tags" or whatever you want to call it.

@kkthxbye-code commented on GitHub (Jul 31, 2023): My personal opinion is that this isn't a great idea. We use tags on device types and we use tags on devices, and they can differ. Tags on devicetypes apply to all the devices of that devicetype, while individual devices of that devicetype can have different tags based on different characteristics. If we were to do this, I think we should retain the current functionality, but provide a new field with "Replicated tags" or whatever you want to call it.
adam commented 2025-12-29 20:36:09 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 4, 2023):

A tag, such as "End of Sale - Nov 2023", can be then applied to any devices created as they come into the warehouse and will be visible on a list without further edits.

But this designation applies to the device type, not the individual devices. For example, it wouldn't make sense to label one device EoS and not label another of the same model. I suggest keeping the tags on the device type, and then filtering devices by those types to find all affected devices.

@jeremystretch commented on GitHub (Aug 4, 2023): > A tag, such as "End of Sale - Nov 2023", can be then applied to any devices created as they come into the warehouse and will be visible on a list without further edits. But this designation applies to the device _type_, not the individual devices. For example, it wouldn't make sense to label one device EoS and not label another of the same model. I suggest keeping the tags on the device type, and then filtering devices by those types to find all affected devices.
adam commented 2025-12-29 20:36:09 +01:00
Author
Owner
Copy Link

@ekrichbaum commented on GitHub (Aug 4, 2023):

The reason it came up was that a tenant filtered list of inventory can show tags but wouldn't in that case. Someone would have to either a.) know that a particular device type has a tag, or b.) manually look up each type of device and add tags to the exported inventory.

Right now, one process is to create the device, assign the same tags. Another is to filter all devices from the device type and bulk add the tags. Neither are horrible, just an extra step. The thought being if I am creating a new device, that step should be removed. Not even considering the second case.

@ekrichbaum commented on GitHub (Aug 4, 2023): The reason it came up was that a tenant filtered list of inventory can show tags but wouldn't in that case. Someone would have to either a.) know that a particular device type has a tag, or b.) manually look up each type of device and add tags to the exported inventory. Right now, one process is to create the device, assign the same tags. Another is to filter all devices from the device type and bulk add the tags. Neither are horrible, just an extra step. The thought being if I am creating a new device, that step should be removed. Not even considering the second case.
adam commented 2025-12-29 20:36:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 24, 2023):

Closing this out due to the opposition as noted above.

@jeremystretch commented on GitHub (Aug 24, 2023): Closing this out due to the opposition as noted above.
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#8393
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?