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

Interfaces Table - bring back the visual aids from v2.9 #5164

New Issue
Closed
opened 2025-12-29 19:24:58 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:24:58 +01:00
Owner
Copy Link

Originally created by @teixemf on GitHub (Aug 10, 2021).

Originally assigned to: @teixemf on GitHub.

NetBox version

v3.0-dev

Feature type

Change to existing functionality

Proposed functionality

In v2.9:

  1. Virtual interfaces were distinguished by their yellow row color.
  2. Disabled interfaces were distinguished by their red row color.
  3. Connected interfaces were distinguished by their green row color.
  4. The interface type was distinguished by different icons before the interface name:
  • Circle for virtual interfaces
  • "Hamburger" for LAG interfaces
  • Wrench for OOB Management interface
  • Wifi symbol for wifi links
  • Two arrows for ethernet links and others

image

This is something that got lost somewhere in v2.10 or v2.11.

v2.11
image

v3.0-dev
image

  • All interfaces, virtual and physical have the same row color. Only connected interfaces get a green row color.
  • All interfaces, despite their type, have the same icon before the interface name.
  • To find the OOB Management interface, one needs to enable the "Management Only" column.
  • To find the enabled interfaces, one needs to enable the "Enabled" column.

This FR proposes to bring back the visual aids that helped get instant information by looking at the interfaces table without overwhelming it with the columns: "Management Only", "Enabled" and "Type".
This FR does not intent to remove the option of having those columns. They are still useful to order the interfaces.

Use case

Reduce the need of the columns "Management Only", "Enabled" and "Type" on the Interfaces table by adding some visual aids that were used on past versions (v2.9).

  1. Virtual interfaces could be distinguished by their yellow row color.
  2. Disabled interfaces were distinguished by their red row color.
  3. Connected interfaces were distinguished by their green row color.
  4. The interface type was distinguished by different icons before the interface name.

With this feature, one can instantly get information about the interface type and status by looking at the interfaces table.
No need to overwhelm the interfaces table with extra columns: "Management Only", "Enabled" and "Type"
These columns should still be available to be added to the interfaces tables. They are useful to order the interfaces.

Database changes

No response

External dependencies

No response

Originally created by @teixemf on GitHub (Aug 10, 2021). Originally assigned to: @teixemf on GitHub. ### NetBox version v3.0-dev ### Feature type Change to existing functionality ### Proposed functionality In v2.9: 1. Virtual interfaces were distinguished by their yellow row color. 2. Disabled interfaces were distinguished by their red row color. 3. Connected interfaces were distinguished by their green row color. 4. The interface type was distinguished by different icons before the interface name: - Circle for virtual interfaces - "Hamburger" for LAG interfaces - Wrench for OOB Management interface - Wifi symbol for wifi links - Two arrows for ethernet links and others ![image](https://user-images.githubusercontent.com/816267/128840831-c37cd6f1-decf-48da-a0dc-0c4717d8e451.png) This is something that got lost somewhere in v2.10 or v2.11. v2.11 ![image](https://user-images.githubusercontent.com/816267/128841865-9b0d8145-23fe-4e17-8000-bf1a00684b55.png) v3.0-dev ![image](https://user-images.githubusercontent.com/816267/128842016-0685ff22-0898-4f4d-a963-743b46192984.png) - All interfaces, virtual and physical have the same row color. Only connected interfaces get a green row color. - All interfaces, despite their type, have the same icon before the interface name. - To find the OOB Management interface, one needs to enable the "Management Only" column. - To find the enabled interfaces, one needs to enable the "Enabled" column. This FR proposes to bring back the visual aids that helped get instant information by looking at the interfaces table without overwhelming it with the columns: "Management Only", "Enabled" and "Type". This FR does not intent to remove the option of having those columns. They are still useful to order the interfaces. ### Use case Reduce the need of the columns "Management Only", "Enabled" and "Type" on the Interfaces table by adding some visual aids that were used on past versions (v2.9). 1. Virtual interfaces could be distinguished by their yellow row color. 2. Disabled interfaces were distinguished by their red row color. 3. Connected interfaces were distinguished by their green row color. 4. The interface type was distinguished by different icons before the interface name. With this feature, one can instantly get information about the interface type and status by looking at the interfaces table. No need to overwhelm the interfaces table with extra columns: "Management Only", "Enabled" and "Type" These columns should still be available to be added to the interfaces tables. They are useful to order the interfaces. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:24:58 +01:00
adam closed this issue 2025-12-29 19:24:58 +01:00
adam commented 2025-12-29 19:24:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 11, 2021):

This is something that got lost somewhere in v2.10 or v2.11.

The change was made when we migrated the device component tables from template-based rendering to proper Table classes using django-tables2. AFAIK it should be possible to replicate the old behavior, however any proposed implementation would need to employ the current classes (e.g. not revert to using raw templates) in an efficient and maintainable manner.

@jeremystretch commented on GitHub (Aug 11, 2021): > This is something that got lost somewhere in v2.10 or v2.11. The change was made when we migrated the device component tables from template-based rendering to proper Table classes using django-tables2. AFAIK it should be possible to replicate the old behavior, however any proposed implementation would need to employ the current classes (e.g. not revert to using raw templates) in an efficient and maintainable manner.
adam commented 2025-12-29 19:25:00 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 10, 2021):

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. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Oct 10, 2021): 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. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:25:00 +01:00
Author
Owner
Copy Link

@teixemf commented on GitHub (Oct 12, 2021):

I believe this FR and #7497 complement each other.
One focus in recall more space from rows the other from columns.

@teixemf commented on GitHub (Oct 12, 2021): I believe this FR and #7497 complement each other. One focus in recall more space from rows the other from columns.
adam commented 2025-12-29 19:25:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 12, 2021):

@CironAkono are you interested in volunteering to implement this?

@jeremystretch commented on GitHub (Oct 12, 2021): @CironAkono are you interested in volunteering to implement this?
adam commented 2025-12-29 19:25:00 +01:00
Author
Owner
Copy Link

@teixemf commented on GitHub (Oct 17, 2021):

@CironAkono are you interested in volunteering to implement this?

@jeremystretch my experience doesn't go beyond simple python scripts. But I can give it a try.

From the Use Case bullet points, I already know how to fix 4.
3. is already working as expected and It may give me some clues on how to fix 1. and 2.
You can sign me up.

@teixemf commented on GitHub (Oct 17, 2021): > @CironAkono are you interested in volunteering to implement this? @jeremystretch my experience doesn't go beyond simple python scripts. But I can give it a try. From the Use Case bullet points, I already know how to fix 4. 3. is already working as expected and It may give me some clues on how to fix 1. and 2. You can sign me up.
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#5164
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?