starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Copy Modules while copying device #6521

New Issue
Closed
opened 2025-12-29 19:41:56 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:41:56 +01:00
Owner
Copy Link

Originally created by @saya6k on GitHub (May 31, 2022).

NetBox version

3.2.3v

Feature type

New functionality

Proposed functionality

Please Copy equipped module with device while device is alreasy filled with modules.

Use case

While Copying Device with all module equipped(Not device type), I have to insert all the same modules to module bay slot.

However there are many use cases to duplicate Device, such as purchasing same hardware with exact same interface cards to use as same purpose.

Database changes

No response

External dependencies

No response

Originally created by @saya6k on GitHub (May 31, 2022). ### NetBox version 3.2.3v ### Feature type New functionality ### Proposed functionality Please Copy equipped module with device while device is alreasy filled with modules. ### Use case While Copying Device with all module equipped(Not device type), I have to insert all the same modules to module bay slot. However there are many use cases to duplicate Device, such as purchasing same hardware with exact same interface cards to use as same purpose. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 19:41:56 +01:00
adam closed this issue 2025-12-29 19:41:56 +01:00
adam commented 2025-12-29 19:41:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 31, 2022):

NetBox currently does not replicate any related objects when cloning an object, partly because of the complex workflow that would be required to do so and partly to avoid unpleasant surprises.

@jeremystretch commented on GitHub (May 31, 2022): NetBox currently does not replicate _any_ related objects when cloning an object, partly because of the complex workflow that would be required to do so and partly to avoid unpleasant surprises.
adam commented 2025-12-29 19:41:57 +01:00
Author
Owner
Copy Link

@mgoetze5 commented on GitHub (Jun 2, 2022):

I do think that copying all related objects (interfaces, modules, power ports, etc.) would be more useful than copying none of them. If I didn't want to copy them I could create a new device instead of copying an existing one.

@mgoetze5 commented on GitHub (Jun 2, 2022): I do think that copying all related objects (interfaces, modules, power ports, etc.) would be more useful than copying none of them. If I didn't want to copy them I could create a new device instead of copying an existing one.
adam commented 2025-12-29 19:41:57 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 2, 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 (Aug 2, 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).
adam commented 2025-12-29 19:41:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 16, 2022):

Closing this out as this FR is not actionable in its current form and there has been no effort to improve it. If anyone would like to devise and propose a detailed implementation plan, you are welcome to do so in a new FR.

@jeremystretch commented on GitHub (Aug 16, 2022): Closing this out as this FR is not actionable in its current form and there has been no effort to improve it. If anyone would like to devise and propose a detailed implementation plan, you are welcome to do so in a new FR.
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 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#6521
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?