Add "Provider" to "Connection" column in device interfaces list #8334

Closed
opened 2025-12-29 20:35:27 +01:00 by adam · 2 comments
Owner

Originally created by @swoga on GitHub (Jul 13, 2023).

NetBox version

v3.5.6

Feature type

Change to existing functionality

Proposed functionality

If an interface is connected to a provider network, only the name of the network is displayed in the interface list of the device.
The name of the provider should also be displayed in the "Connection" column.

mockup:
image

This request is similar to #10748.

Use case

The network name can be non-unique or non-descriptive.
Adding the provider name makes it explicit which one it is.
It avoids the duplication of the provider name in the network name (as it is currently done in the demo data).

Database changes

No response

External dependencies

No response

Originally created by @swoga on GitHub (Jul 13, 2023). ### NetBox version v3.5.6 ### Feature type Change to existing functionality ### Proposed functionality If an interface is connected to a provider network, only the name of the network is displayed in the interface list of the device. The name of the provider should also be displayed in the "Connection" column. mockup: ![image](https://github.com/netbox-community/netbox/assets/3697291/dcf22fc0-eb0c-4707-8b8c-16dcaed4b210) This request is similar to #10748. ### Use case The network name can be non-unique or non-descriptive. Adding the provider name makes it explicit which one it is. It avoids the duplication of the provider name in the network name (as it is currently done in the demo data). ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 20:35:27 +01:00
adam closed this issue 2025-12-29 20:35:27 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Oct 12, 2023):

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[bot] commented on GitHub (Oct 12, 2023): 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](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Nov 11, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Nov 11, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8334