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

Clone should also prepopulate custom fields #6147

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

Originally created by @skvedo on GitHub (Feb 25, 2022).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.1.8

Feature type

Change to existing functionality

Proposed functionality

When cloning entity, values from custom fields should be also populated in form.

Use case

Our organization have defined custom fields for prefix with abuse contact to particular tenant IT support staff. When assigning new prefix you usually set these "same as that other segment" so using clone button is obvious approach.

Database changes

Might be good idea add this fields to prefix form.
We defined 2 fields:

  • security abuse contact for case of incident which should be taken case ASAP. Usually creates an incident ticket
  • administrative contact if you need contact for particular tenant. Usually this is pointed to teams mailing list.

External dependencies

No response

Originally created by @skvedo on GitHub (Feb 25, 2022). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.1.8 ### Feature type Change to existing functionality ### Proposed functionality When cloning entity, values from custom fields should be also populated in form. ### Use case Our organization have defined custom fields for prefix with abuse contact to particular tenant IT support staff. When assigning new prefix you usually set these "same as that other segment" so using clone button is obvious approach. ### Database changes Might be good idea add this fields to prefix form. We defined 2 fields: * security abuse contact for case of incident which should be taken case ASAP. Usually creates an incident ticket * administrative contact if you need contact for particular tenant. Usually this is pointed to teams mailing list. ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:37:21 +01:00
adam closed this issue 2025-12-29 19:37:21 +01:00
adam commented 2025-12-29 19:37:21 +01:00
Author
Owner
Copy Link

@IdRatherStand commented on GitHub (Mar 14, 2022):

I also have users coming to me within our org asking if there is an option to turn this on (we have a very similar use case) so gets a thumbs up from me (y)

@IdRatherStand commented on GitHub (Mar 14, 2022): I also have users coming to me within our org asking if there is an option to turn this on (we have a very similar use case) so gets a thumbs up from me (y)
adam commented 2025-12-29 19:37:21 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 14, 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. Please see our contributing guide.

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

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

Blocked by #9414

@jeremystretch commented on GitHub (May 24, 2022): Blocked by #9414
adam commented 2025-12-29 19:37:22 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Nov 4, 2022):

@jeremystretch I'm thinking we wouldn't want this for all custom fields, what about an "is_clonable" flag added to custom fields (default False) if set it will copy over when cloning the related object?

@arthanson commented on GitHub (Nov 4, 2022): @jeremystretch I'm thinking we wouldn't want this for all custom fields, what about an "is_clonable" flag added to custom fields (default False) if set it will copy over when cloning the related object?
adam commented 2025-12-29 19:37:22 +01:00
Author
Owner
Copy Link

@hagbarddenstore commented on GitHub (Nov 4, 2022):

Arthur, that would suit our use cases perfectly. Some custom fields are used to determine which SLA we’re using, which could be cloned. Other fields are used to store external identifiers, which shouldn’t be cloned as they are unique per object in NetBox.

@hagbarddenstore commented on GitHub (Nov 4, 2022): Arthur, that would suit our use cases perfectly. Some custom fields are used to determine which SLA we’re using, which could be cloned. Other fields are used to store external identifiers, which shouldn’t be cloned as they are unique per object in NetBox.
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: accepted 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#6147
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?