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

Ability to clone a device with a different name. #527

New Issue
Closed
opened 2025-12-29 16:22:53 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:22:53 +01:00
Owner
Copy Link

Originally created by @phobiadhs on GitHub (Nov 9, 2016).

This is low priority but still important in my eyes as adding the device manually isn't exactly difficult. As it is now though, it takes many repeating clicks to assign the required fields for each new device assuming you are creating many similar devices.

What I suggest is the ability to clone a device, replicating Device Role, Manufacturer and Device Type all by default.

Obviously a new Name will be required and I believe when that name is entered, the ability to select a site and rack should also be available, likely with the defaults being the cloned devices values.

This could save a good number of clicks and/or tabs for each similar device entry and make the overall workflow considerably more efficient when adding many new similar devices.

Originally created by @phobiadhs on GitHub (Nov 9, 2016). This is low priority but still important in my eyes as adding the device manually isn't exactly difficult. As it is now though, it takes many repeating clicks to assign the required fields for each new device assuming you are creating many similar devices. What I suggest is the ability to clone a device, replicating Device Role, Manufacturer and Device Type all by default. Obviously a new Name will be required and I believe when that name is entered, the ability to select a site and rack should also be available, likely with the defaults being the cloned devices values. This could save a good number of clicks and/or tabs for each similar device entry and make the overall workflow considerably more efficient when adding many new similar devices.
adam added the status: duplicate label 2025-12-29 16:22:53 +01:00
adam closed this issue 2025-12-29 16:22:53 +01:00
adam commented 2025-12-29 16:22:54 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 10, 2016):

To clarify, you're asking for the ability to select a device that has already been created, and pre-populate most of its data in a form to create a new device?

(This is probably related to #648, but that deals only with creating multiple devices in immediate succession.)

@jeremystretch commented on GitHub (Nov 10, 2016): To clarify, you're asking for the ability to select a device that has already been created, and pre-populate most of its data in a form to create a new device? (This is probably related to #648, but that deals only with creating multiple devices in immediate succession.)
adam commented 2025-12-29 16:22:54 +01:00
Author
Owner
Copy Link

@phobiadhs commented on GitHub (Nov 10, 2016):

You are correct.

I would like to select a device, hit a "Clone" button and have the above mentioned fields be pre populated in the new device with only the name and the rack left to manually enter or select.

As the point of this enhancement is to increase efficiency in workflow, I would suggest that the cloned fields are handled in the background so the user doesn't get bogged down in the details of a cloned device as it is being created. Fill in Name, select Rack. Presto, cloned device created.

Looking at #648, they are related but the usage is a bit different as you said.

@phobiadhs commented on GitHub (Nov 10, 2016): You are correct. I would like to select a device, hit a "Clone" button and have the above mentioned fields be pre populated in the new device with only the name and the rack left to manually enter or select. As the point of this enhancement is to increase efficiency in workflow, I would suggest that the cloned fields are handled in the background so the user doesn't get bogged down in the details of a cloned device as it is being created. Fill in Name, select Rack. Presto, cloned device created. Looking at #648, they are related but the usage is a bit different as you said.
adam commented 2025-12-29 16:22:54 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 22, 2016):

This actually seems to be a duplicate of #33.

@jeremystretch commented on GitHub (Nov 22, 2016): This actually seems to be a duplicate of #33.
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: duplicate
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#527
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?