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

Enable Custom Fields on Circuit Terminations #6035

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

Originally created by @ryanmerolle on GitHub (Feb 1, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.1.6

Feature type

Change to existing functionality

Proposed functionality

It may be useful to associate various custom fields to a circuit termination. You cannot do this currently.

Use case

Let's say you document cross-connect monthly charges, term length, and install fees. Right now you would have to associate that to the circuit because circuit terminations do not allow custom fields. The challenge is that if you have a point to point, you would then associate said custom fields to the related circuit, which is not truly correct.

Database changes

No response

External dependencies

No response

Originally created by @ryanmerolle on GitHub (Feb 1, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.1.6 ### Feature type Change to existing functionality ### Proposed functionality It may be useful to associate various custom fields to a circuit termination. You cannot do this currently. ### Use case Let's say you document cross-connect monthly charges, term length, and install fees. Right now you would have to associate that to the circuit because circuit terminations do not allow custom fields. The challenge is that if you have a point to point, you would then associate said custom fields to the related circuit, which is not truly correct. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:35:55 +01:00
adam closed this issue 2025-12-29 19:35:55 +01:00
adam commented 2025-12-29 19:35:56 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 3, 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 (Apr 3, 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:35:56 +01:00
Author
Owner
Copy Link

@tyler-8 commented on GitHub (Apr 15, 2022):

I can think of several use cases that would be helped by having Custom Object Fields tied to Circuit Terminations - not to mention the "regular" custom fields.

It would help with "virtual circuits" by being able to attach an IP (or L3 Interface) to a CircuitTermination if the physical termination is on a different device. That's would be a huge win IMO.

@tyler-8 commented on GitHub (Apr 15, 2022): I can think of several use cases that would be helped by having Custom Object Fields tied to Circuit Terminations - not to mention the "regular" custom fields. It would help with "virtual circuits" by being able to attach an IP (or L3 Interface) to a `CircuitTermination` if the physical termination is on a different device. That's would be a huge win IMO.
adam commented 2025-12-29 19:35:56 +01:00
Author
Owner
Copy Link

@proudbro commented on GitHub (Apr 20, 2022):

Very necessary functionality! We are really looking forward to it.
Especially now, when these issues (1, 2) were rejected, it is able to be the only way for modelling interconnections between racks by using related custom fields.

@proudbro commented on GitHub (Apr 20, 2022): Very necessary functionality! We are really looking forward to it. Especially now, when these issues ([1](https://github.com/netbox-community/netbox/issues/9172), [2](https://github.com/netbox-community/netbox/issues/9173)) were rejected, it is able to be the only way for modelling interconnections between racks by using related custom fields.
adam commented 2025-12-29 19:35:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 20, 2022):

it is able to be the only way for modelling interconnections between racks by using related custom fields.

I describe an approach in my comment on #9172 that would work very well without relying on custom fields.

@jeremystretch commented on GitHub (Apr 20, 2022): > it is able to be the only way for modelling interconnections between racks by using related custom fields. I describe an approach in my comment on #9172 that would work very well without relying on custom fields.
adam commented 2025-12-29 19:35:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 1, 2022):

I'm going to add support for tags as part of this work as well.

@jeremystretch commented on GitHub (Jul 1, 2022): I'm going to add support for tags as part of this work as well.
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#6035
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?