clone device type does not clone components #6195

Closed
opened 2025-12-29 19:37:54 +01:00 by adam · 3 comments
Owner

Originally created by @petersonbasso on GitHub (Mar 10, 2022).

NetBox version

v3.1.9

Feature type

Change to existing functionality

Proposed functionality

the clone button in device types, should clone all created components.

Use case

The idea behind cloning an object is to take advantage of everything already created previously, currently the clone is only taking advantage of basic information, leaving this option with little use.

Database changes

No response

External dependencies

No response

Originally created by @petersonbasso on GitHub (Mar 10, 2022). ### NetBox version v3.1.9 ### Feature type Change to existing functionality ### Proposed functionality the clone button in device types, should clone all created components. ### Use case The idea behind cloning an object is to take advantage of everything already created previously, currently the clone is only taking advantage of basic information, leaving this option with little use. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:37:54 +01:00
adam closed this issue 2025-12-29 19:37:54 +01:00
Author
Owner

@jeremystretch commented on GitHub (Mar 10, 2022):

This was proposed in #4065 and again in #5536, but no one was interested in owning the implementation. If you would like to own this and commit to delivering a PR, I'll gladly assign it to you. Otherwise, it will be closed as a duplicate.

@jeremystretch commented on GitHub (Mar 10, 2022): This was proposed in #4065 and again in #5536, but no one was interested in owning the implementation. If you would like to own this and commit to delivering a PR, I'll gladly assign it to you. Otherwise, it will be closed as a duplicate.
Author
Owner

@petersonbasso commented on GitHub (Mar 10, 2022):

Isn't it better to leave it open? How will people be interested if the issue is not open.

@petersonbasso commented on GitHub (Mar 10, 2022): Isn't it better to leave it open? How will people be interested if the issue is not open.
Author
Owner

@jeremystretch commented on GitHub (Mar 10, 2022):

Issues are allowed to remain open for three months. In that time, if no one has expressed interest in owning it, the issue is closed as stale to ensure we don't amass hundreds of inactive issues. People can still find it when searching.

@jeremystretch commented on GitHub (Mar 10, 2022): Issues are allowed to remain open for three months. In that time, if no one has expressed interest in owning it, the issue is closed as stale to ensure we don't amass hundreds of inactive issues. People can still find it when searching.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6195