Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cable trace: include circuit "description" field #12831

Closed
candlerb opened this issue Jun 7, 2023 · 1 comment
Closed

Cable trace: include circuit "description" field #12831

candlerb opened this issue Jun 7, 2023 · 1 comment
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@candlerb
Copy link
Contributor

candlerb commented Jun 7, 2023

NetBox version

v3.5.3

Feature type

Change to existing functionality

Proposed functionality

When doing an end-to-end trace which includes a Circuit, the Circuit element shows:

,---------------------------.
|<Circuit ID>: termination A|
+---------------------------+
|   Circuit <Circuit ID>    |
|   <Provider>              |
+---------------------------+
|<Circuit ID>: termination Z|
`---------------------------'

I would like the middle box to include the circuit description field as well (if it is set)

Use case

A circuit ID by itself is an opaque number, whereas the circuit description gives a human-readable summary of its purpose.

Our current workaround is to abuse the Circuit ID field with "<Circuit ID> - <Description>", although this means that now the description is duplicated in the termination A and termination Z fields.

Database changes

None

External dependencies

None

@candlerb candlerb added the type: feature Introduction of new functionality to the application label Jun 7, 2023
candlerb added a commit to candlerb/netbox that referenced this issue Jun 7, 2023
candlerb added a commit to candlerb/netbox that referenced this issue Jun 7, 2023
@jeremystretch jeremystretch added the status: under review Further discussion is needed to determine this issue's scope and/or implementation label Jun 12, 2023
@github-actions
Copy link
Contributor

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Sep 11, 2023
@jeremystretch jeremystretch self-assigned this Oct 6, 2023
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation pending closure Requires immediate attention to avoid being closed for inactivity labels Oct 6, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants