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

Add ID/Description/Comments field to circuit terminations #685

New Issue
Closed
opened 2025-12-29 16:24:46 +01:00 by adam · 4 comments
adam commented 2025-12-29 16:24:46 +01:00
Owner
Copy Link

Originally created by @alexjhart on GitHub (Feb 1, 2017).

In addition to a circuit having an ID (that field already exists), it is common for each termination (A and Z sides) to have their own unique IDs as well (think UNI ID). This could just be added as a text field with the name "ID", but I could see the benefit of having a more generic field if people have other information they want to track.

Originally created by @alexjhart on GitHub (Feb 1, 2017). In addition to a circuit having an ID (that field already exists), it is common for each termination (A and Z sides) to have their own unique IDs as well (think UNI ID). This could just be added as a text field with the name "ID", but I could see the benefit of having a more generic field if people have other information they want to track.
adam added the status: acceptedtype: feature labels 2025-12-29 16:24:46 +01:00
adam closed this issue 2025-12-29 16:24:46 +01:00
adam commented 2025-12-29 16:24:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 13, 2017):

As it is, we've got description and text fields on the circuit itself. Might this be overkill?

@jeremystretch commented on GitHub (Feb 13, 2017): As it is, we've got description and text fields on the circuit itself. Might this be overkill?
adam commented 2025-12-29 16:24:46 +01:00
Author
Owner
Copy Link

@alexjhart commented on GitHub (Feb 13, 2017):

The description and text fields are only for the circuit. I'm talking about the termination, not circuit (A/Z side). I certainly don't think this is overkill. I'd be curious to hear from others. I hope I did a good enough job of stating the case for this.

Without making this enhancement, I'm left entering something like this in the comments field of the circuit:
Site X (termination A) ID: xxxyyyzzz
Site Y (termination Z) ID: yyyzzzxxx

That seems like more data entry than should be required and doesn't tie the information to the object it pertains to.

I imagine this will get added right below the patch panel/port field.

@alexjhart commented on GitHub (Feb 13, 2017): The description and text fields are only for the circuit. I'm talking about the termination, not circuit (A/Z side). I certainly don't think this is overkill. I'd be curious to hear from others. I hope I did a good enough job of stating the case for this. Without making this enhancement, I'm left entering something like this in the comments field of the circuit: Site X (termination A) ID: xxxyyyzzz Site Y (termination Z) ID: yyyzzzxxx That seems like more data entry than should be required and doesn't tie the information to the object it pertains to. I imagine this will get added right below the patch panel/port field.
adam commented 2025-12-29 16:24:47 +01:00
Author
Owner
Copy Link

@muddus commented on GitHub (Apr 24, 2017):

Or the option to add custom fields to circuit termination form just like the circuit.

@muddus commented on GitHub (Apr 24, 2017): Or the option to add custom fields to circuit termination form just like the circuit.
adam commented 2025-12-29 16:24:47 +01:00
Author
Owner
Copy Link

@alexjhart commented on GitHub (May 11, 2017):

That would work too

@alexjhart commented on GitHub (May 11, 2017): That would work too
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#685
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?