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 viewing unique ID of connections #68

New Issue
Closed
opened 2025-12-29 15:31:19 +01:00 by adam · 3 comments
adam commented 2025-12-29 15:31:19 +01:00
Owner
Copy Link

Originally created by @mdomore on GitHub (Jun 29, 2016).

When we are in the connections section, is it possible to add a/the unique id of the connection it can be usefull for labelling cables.

Originally created by @mdomore on GitHub (Jun 29, 2016). When we are in the connections section, is it possible to add a/the unique id of the connection it can be usefull for labelling cables.
adam added the status: duplicate label 2025-12-29 15:31:19 +01:00
adam closed this issue 2025-12-29 15:31:19 +01:00
adam commented 2025-12-29 15:31:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 29, 2016):

Are you referring to the primary key which represents the connection in the database? I would strongly recommend against using this for anything real-world, as it's really only significant within NetBox.

We do plan to implement fields for patch cable labeling as part of the initiative to start tracking physical cable plants.

@jeremystretch commented on GitHub (Jun 29, 2016): Are you referring to the primary key which represents the connection in the database? I would strongly recommend against using this for anything real-world, as it's really only significant within NetBox. We do plan to implement fields for patch cable labeling as part of the initiative to start tracking physical cable plants.
adam commented 2025-12-29 15:31:20 +01:00
Author
Owner
Copy Link

@mdomore commented on GitHub (Jun 30, 2016):

I was using a personal ipam solution but i'm not a dev so there was a lot of bug and not a lot of features. But i was generating a single id for each connection/cable enter in the ipam so i can have a reference.

Using a template to generate a unique label for cables and save it in netbox for reference could be usefull.

@mdomore commented on GitHub (Jun 30, 2016): I was using a personal ipam solution but i'm not a dev so there was a lot of bug and not a lot of features. But i was generating a single id for each connection/cable enter in the ipam so i can have a reference. Using a template to generate a unique label for cables and save it in netbox for reference could be usefull.
adam commented 2025-12-29 15:31:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 20, 2016):

Closing this as a duplicate since it's sure to be covered by #20.

@jeremystretch commented on GitHub (Jul 20, 2016): Closing this as a duplicate since it's sure to be covered by #20.
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: duplicate
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#68
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?