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

Circuit ID should not be mandatory or be allowed empty #6065

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

Originally created by @jasonyates on GitHub (Feb 7, 2022).

NetBox version

3.1.7

Feature type

Change to existing functionality

Proposed functionality

Proposing that the 'Circuit ID' field should not be mandatory and/or be permitted as a Null value if it is to remain mandatory.

Use case

A new circuit with a status of Planned or Provisioning is highly unlikely to have a CID assigned by the carrier. At present we have to use our TEM tool's order ID in place of a CID so that we can track a circuit order in Netbox which is less than ideal.

Database changes

No response

External dependencies

No response

Originally created by @jasonyates on GitHub (Feb 7, 2022). ### NetBox version 3.1.7 ### Feature type Change to existing functionality ### Proposed functionality Proposing that the 'Circuit ID' field should not be mandatory and/or be permitted as a Null value if it is to remain mandatory. ### Use case A new circuit with a status of Planned or Provisioning is highly unlikely to have a CID assigned by the carrier. At present we have to use our TEM tool's order ID in place of a CID so that we can track a circuit order in Netbox which is less than ideal. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: under review labels 2025-12-29 19:36:17 +01:00
adam closed this issue 2025-12-29 19:36:17 +01:00
adam commented 2025-12-29 19:36:17 +01:00
Author
Owner
Copy Link

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

I think the major issue you run into here is that you need some form of identifier for the circuit, even if it has yet to be provisioned.

@jeremystretch commented on GitHub (Mar 30, 2022): I think the major issue you run into here is that you need _some_ form of identifier for the circuit, even if it has yet to be provisioned.
adam commented 2025-12-29 19:36:18 +01:00
Author
Owner
Copy Link

@jasonyates commented on GitHub (Apr 11, 2022):

I think the major issue you run into here is that you need some form of identifier for the circuit, even if it has yet to be provisioned.

Why?
If I order a circuit with a carrier, they don't assign a CID until the order is delivered or close to being delivered, in the meantime I have no unique identifier for the circuit and so I can't track it in Netbox as provisioning. I also can't use something generic like "Ordered" or "Unknown" as the model enforces a unique CID.

Is there any reason this couldn't be turned in to a user configuration option similar to ENFORCE_GLOBAL_UNIQUE ? Leave it default to True but allow users to have the flexibility of disabling it and then display something similar to "Unnamed device".

@jasonyates commented on GitHub (Apr 11, 2022): > I think the major issue you run into here is that you need _some_ form of identifier for the circuit, even if it has yet to be provisioned. Why? If I order a circuit with a carrier, they don't assign a CID until the order is delivered or close to being delivered, in the meantime I have no unique identifier for the circuit and so I can't track it in Netbox as provisioning. I also can't use something generic like "Ordered" or "Unknown" as the model enforces a unique CID. Is there any reason this couldn't be turned in to a user configuration option similar to ENFORCE_GLOBAL_UNIQUE ? Leave it default to True but allow users to have the flexibility of disabling it and then display something similar to "Unnamed device".
adam commented 2025-12-29 19:36:18 +01:00
Author
Owner
Copy Link

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

Why?

What does a list of circuits with no circuit IDs look like in a form? How can you tell which is which?

@jeremystretch commented on GitHub (Apr 11, 2022): > Why? What does a list of circuits with no circuit IDs look like in a form? How can you tell which is which?
adam commented 2025-12-29 19:36:18 +01:00
Author
Owner
Copy Link

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

Closing this out as it does not seem feasible to implement.

@jeremystretch commented on GitHub (May 24, 2022): Closing this out as it does not seem feasible to implement.
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: under review 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#6065
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?