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

Allow Export Templates for Circuit Terminations and Virtual Circuit Terminations #11125

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

Originally created by @KPTheProf on GitHub (May 6, 2025).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.3.0-Docker-3.2.1

Feature type

New functionality

Proposed functionality

Whilst there is the ability to export Circuit Terminations and Virtual Circuit Terminations using the Export / All Data (CSV), there is no way to export the data in a format that can be used to ingest back into Netbox using export templates.

The object type Circuits > Circuit Terminations and Circuits > Virtual Circuit Terminations are not available when creating and Export Template.

This was originally raised as a bug https://github.com/netbox-community/netbox/issues/19387 but was rejected, so I'm raising this as a request for this needed feature.

Use case

This will allow the exporting of (Virtual) Circuit Terminations in a format that can be worked on and amended and re-imported back into Netbox when creating new (virtual) circuits or amending existing ones.

Currently, the exported data from Export / All Data (CSV) report has to have all its headers amended into the required format for reimporting back into Netbox as this export is not in a suitable format for re-importing back into Netbox.

Database changes

None

External dependencies

None

Originally created by @KPTheProf on GitHub (May 6, 2025). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.3.0-Docker-3.2.1 ### Feature type New functionality ### Proposed functionality Whilst there is the ability to export Circuit Terminations and Virtual Circuit Terminations using the Export / All Data (CSV), there is no way to export the data in a format that can be used to ingest back into Netbox using export templates. The object type Circuits > Circuit Terminations and Circuits > Virtual Circuit Terminations are not available when creating and Export Template. This was originally raised as a bug https://github.com/netbox-community/netbox/issues/19387 but was rejected, so I'm raising this as a request for this needed feature. ### Use case This will allow the exporting of (Virtual) Circuit Terminations in a format that can be worked on and amended and re-imported back into Netbox when creating new (virtual) circuits or amending existing ones. Currently, the exported data from Export / All Data (CSV) report has to have all its headers amended into the required format for reimporting back into Netbox as this export is not in a suitable format for re-importing back into Netbox. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:40:40 +01:00
adam closed this issue 2025-12-29 21:40:41 +01:00
adam commented 2025-12-29 21:40:41 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (May 8, 2025):

This seems like a good case for a plugin

@arthanson commented on GitHub (May 8, 2025): This seems like a good case for a plugin
adam commented 2025-12-29 21:40:42 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 7, 2025):

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 7, 2025): 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/main/CONTRIBUTING.md).
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 complexity: low 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#11125
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?