Add Virtual Chassis name to pane on Device View #11032

New Issue

adam · 2025-12-29T21:39:23+01:00

adam commented

2025-12-29 21:39:23 +01:00

Originally created by @cmcknz77 on GitHub (Apr 15, 2025).

Originally assigned to: @renatoalmeidaoliveira on GitHub.

NetBox version

v4.2.6

Feature type

Change to existing functionality

Proposed functionality

I propose an amendment to the device view template

to add {{ object.virtual_chassis.name }} to the prefetch list and add the following to the h2 Header for the Virtual Chassis section:

Here's what it might look like (although I've had to redact some info):

{% if vc_members %}
                <div class="card">
                    <h2 class="card-header">
                      {% trans "Virtual Chassis" %}: {{ object.virtual_chassis.name }}
                      <div class="card-actions">
                        <a href="{{ object.virtual_chassis.get_absolute_url }}" class="btn btn-ghost-primary btn-sm">
                          <span class="mdi mdi-arrow-right-bold" aria-hidden="true"></span> {% trans "View Virtual Chassis" %}
                        </a>
                      </div>
                    </h2>

Use case

I work with a number of Virtual Chassis in my environment and in a lot of cases the member Device Name does not have a direct relationship with the name of the Virtual Chassis that device is a member of to help make the device easily identifiable.

It would be really handy if when a device is a member of a Virtual Chassis, the name of that Virtual Chassis is visible on the device page.

For example in your demo environment the Camden site is connected with 2 SDWAN Redundant devices operating as a single SDWAN Edge with name "NACamdenEdge-VC".

But when you click on the devices themselves there's no way to tell which Edge device it's a member of:

Database changes

None required - this is a purely cosmetic change.

External dependencies

No response

Originally created by @cmcknz77 on GitHub (Apr 15, 2025). Originally assigned to: @renatoalmeidaoliveira on GitHub. ### NetBox version v4.2.6 ### Feature type Change to existing functionality ### Proposed functionality I propose an amendment to the [device view template](https://github.com/netbox-community/netbox/blob/main/netbox/templates/dcim/device.html) ![Image](https://github.com/user-attachments/assets/3d359590-e8e0-4c64-9764-7d5030aa703e) to add `{{ object.virtual_chassis.name }}` to the prefetch list and add the following to the h2 Header for the Virtual Chassis section: ![Image](https://github.com/user-attachments/assets/1e222153-5585-4621-a9a7-549d5e5d551b) Here's what it might look like (although I've had to redact some info): ![Image](https://github.com/user-attachments/assets/33e9b235-70e6-4d7e-8da1-f99048c80272) ```html {% if vc_members %} <div class="card"> <h2 class="card-header"> {% trans "Virtual Chassis" %}: {{ object.virtual_chassis.name }} <div class="card-actions"> <a href="{{ object.virtual_chassis.get_absolute_url }}" class="btn btn-ghost-primary btn-sm"> <span class="mdi mdi-arrow-right-bold" aria-hidden="true"></span> {% trans "View Virtual Chassis" %} </a> </div> </h2> ``` ### Use case I work with a number of Virtual Chassis in my environment and in a lot of cases the member Device Name does not have a direct relationship with the name of the Virtual Chassis that device is a member of to help make the device easily identifiable. It would be really handy if when a device is a member of a Virtual Chassis, the name of that Virtual Chassis is visible on the device page. For example in your demo environment the Camden site is connected with 2 SDWAN Redundant devices operating as a single SDWAN Edge with name "NACamdenEdge-VC". ![Image](https://github.com/user-attachments/assets/8af0f079-deb8-4b0b-aab7-b274159696b8) But when you click on the devices themselves there's no way to tell which Edge device it's a member of: ![Image](https://github.com/user-attachments/assets/2cc9f3de-4723-4a02-89f0-64929165d106) ### Database changes None required - this is a purely cosmetic change. ### External dependencies _No response_

adam added the status: accepted type: feature complexity: low labels 2025-12-29 21:39:23 +01:00

adam closed this issue

2025-12-29 21:39:23 +01:00

adam commented

2025-12-29 21:39:24 +01:00

@jeremystretch commented on GitHub (Apr 28, 2025):

Let's use parentheses instead of a colon to be more consistent with other areas of the UI.

@jeremystretch commented on GitHub (Apr 28, 2025): Let's use parentheses instead of a colon to be more consistent with other areas of the UI.

adam referenced this issue

2025-12-29 23:21:02 +01:00

[PR #11698] [MERGED] Fixes #11032 - Replication fields broken in custom validation #13828

adam referenced this issue

2025-12-29 23:21:07 +01:00

[PR #11793] [MERGED] Release v3.4.5 #13842

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#11032