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

Allow netbox to generate circuit IDs. #1778

New Issue
Closed
opened 2025-12-29 17:19:02 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:19:02 +01:00
Owner
Copy Link

Originally created by @nickzxcv on GitHub (Jun 7, 2018).

Issue type

[ X ] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: 2.3.3

Description

The circuit ID field is mandatory when adding a circuit. In case of "circuits" used within the same organization, such as between cages of the same customer in a colo, it would be useful to have an option for Netbox to generate the ID.

No third party libraries should be needed. This could mean a schema change, or just to use the existing id column in circuits_circuit. In the GUI it could be a checkbox to use the Netbox circuit id, and in the API there could be some word to put in the field that means to use the Netbox id. If the box is checked maybe it would also put the word in the cid field since in the schema it is NOT NULL. Maybe there is a better way than a reserved word?

Originally created by @nickzxcv on GitHub (Jun 7, 2018). ### Issue type [ X ] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> ### Environment * Python version: 3.5.2 * NetBox version: 2.3.3 ### Description The circuit ID field is mandatory when adding a circuit. In case of "circuits" used within the same organization, such as between cages of the same customer in a colo, it would be useful to have an option for Netbox to generate the ID. No third party libraries should be needed. This could mean a schema change, or just to use the existing id column in circuits_circuit. In the GUI it could be a checkbox to use the Netbox circuit id, and in the API there could be some word to put in the field that means to use the Netbox id. If the box is checked maybe it would also put the word in the cid field since in the schema it is NOT NULL. Maybe there is a better way than a reserved word?
adam closed this issue 2025-12-29 17:19:02 +01:00
adam commented 2025-12-29 17:19:02 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 7, 2018):

Sorry but this is firmly out of scope for NetBox. Every organization has their own naming preferences, and I'm not about to go down that rabbit hole.

@jeremystretch commented on GitHub (Jun 7, 2018): Sorry but this is firmly out of scope for NetBox. Every organization has their own naming preferences, and I'm not about to go down that rabbit hole.
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
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#1778
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?