starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Multiple configure table views #8994

New Issue
Closed
opened 2025-12-29 20:43:56 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:43:56 +01:00
Owner
Copy Link

Originally created by @Dakson13 on GitHub (Dec 22, 2023).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.6.7

Feature type

New functionality

Proposed functionality

I propose a functionality that will allow saving different column layout selections to the dropdown menu of the Configure Table pop-up window. This would be useful in cases where there are multiple scenarios, and some columns are not needed to be visible for certain scenarios. For example, in the first scenario, to display a specific type of device, a larger number of columns is required, while for the second scenario, to display a different type of device, a significantly smaller number of columns is needed.

Example: In the first scenario, we list all routers, and the necessary columns are - Name, Status, Role, Type, Serial number, Asset tag, Site, Rack, Tags, Comments; in the second scenario, we list all IP phones, and only the columns - Serial number, Contacts, and the custom field "Price" are necessary.

In the current version, achieving this would require changing the column layout in the Configure Table pop-up window each time, and this would need to be done for each scenario.

The creation of new column layouts and their selection would be performed in the Configure Table pop-up window. Editing would be done in another location, which I will describe below.
I suggest that in the Configure Table pop-up window, desired column layouts for different scenarios be saved as dropdown menu options. This way, when we select the columns needed for display in one of the scenarios, to save the selection we click on a button called, for example, "Save Table View". We would do the same for each subsequent scenario. Regarding the selection of these saved column layouts, it would be done from that dropdown menu within the Configure Table pop-up window. Editing parameters for saved scenarios (found in the dropdown menu) could be similar to Saved Filters (Customization --> Saved Filters), where saved filters can be edited. Something similar could possibly be done for editing "Saved Table Views".

Use case

Implementing this would, for example, streamline and expedite the process of displaying necessary details for different types of devices by enabling or disabling various columns.
Users would be able to swiftly choose between different levels of required details from the dropdown menu.

Database changes

No response

External dependencies

No response

Originally created by @Dakson13 on GitHub (Dec 22, 2023). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.6.7 ### Feature type New functionality ### Proposed functionality I propose a functionality that will allow saving different column layout selections to the dropdown menu of the Configure Table pop-up window. This would be useful in cases where there are multiple scenarios, and some columns are not needed to be visible for certain scenarios. For example, in the first scenario, to display a specific type of device, a larger number of columns is required, while for the second scenario, to display a different type of device, a significantly smaller number of columns is needed. Example: In the first scenario, we list all routers, and the necessary columns are - Name, Status, Role, Type, Serial number, Asset tag, Site, Rack, Tags, Comments; in the second scenario, we list all IP phones, and only the columns - Serial number, Contacts, and the custom field "Price" are necessary. In the current version, achieving this would require changing the column layout in the Configure Table pop-up window each time, and this would need to be done for each scenario. The **creation** of new column layouts and their **selection** would be performed in the Configure Table pop-up window. **Editing** would be done in another location, which I will describe below. I suggest that in the Configure Table pop-up window, desired column layouts for different scenarios be saved as dropdown menu options. This way, when we select the columns needed for display in one of the scenarios, to **save** the selection we click on a button called, for example, "Save Table View". We would do the same for each subsequent scenario. Regarding the **selection** of these saved column layouts, it would be done from that dropdown menu within the Configure Table pop-up window. **Editing** parameters for saved scenarios (found in the dropdown menu) could be similar to Saved Filters (Customization --> Saved Filters), where saved filters can be edited. Something similar could possibly be done for editing "Saved Table Views". ### Use case Implementing this would, for example, streamline and expedite the process of displaying necessary details for different types of devices by enabling or disabling various columns. Users would be able to swiftly choose between different levels of required details from the dropdown menu. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurenetboxcomplexity: high labels 2025-12-29 20:43:56 +01:00
adam closed this issue 2025-12-29 20:43:56 +01:00
adam commented 2025-12-29 20:43:57 +01:00
Author
Owner
Copy Link

@opericgithub commented on GitHub (Dec 23, 2023):

I believe this is an excellent suggestion. We also need to rearrange column layouts frequently. For instance, when listing all equipment under maintenance, we have to include ten different columns and add custom field columns related to the purchase date and maintenance expiration date. On the other hand, when listing only switches, we are only interested in three columns. Having to change column layouts each time is tedious, time-consuming, and prone to errors. This proposed method would allow us to easily and quickly select a column layout suitable for a specific need from the dropdown menu.

@opericgithub commented on GitHub (Dec 23, 2023): I believe this is an excellent suggestion. We also need to rearrange column layouts frequently. For instance, when listing all equipment under maintenance, we have to include ten different columns and add custom field columns related to the purchase date and maintenance expiration date. On the other hand, when listing only switches, we are only interested in three columns. Having to change column layouts each time is tedious, time-consuming, and prone to errors. This proposed method would allow us to easily and quickly select a column layout suitable for a specific need from the dropdown menu.
adam commented 2025-12-29 20:43:57 +01:00
Author
Owner
Copy Link

@chrisattlf commented on GitHub (Jan 17, 2024):

I came here to propose the exact same thing. I'm 100% down for this feature. There have been multiple occasions where I want to look over the devices in a particular set of columns, so far I've been able to get around it with using the export feature to CSV but that grows tiresome after a while. Having the ability to define custom column sets and change the view for devices would be a huge QoL improvement.

@chrisattlf commented on GitHub (Jan 17, 2024): I came here to propose the exact same thing. I'm 100% down for this feature. There have been multiple occasions where I want to look over the devices in a particular set of columns, so far I've been able to get around it with using the export feature to CSV but that grows tiresome after a while. Having the ability to define custom column sets and change the view for devices would be a huge QoL improvement.
adam commented 2025-12-29 20:43:57 +01:00
Author
Owner
Copy Link

@eronlloyd commented on GitHub (Jan 21, 2024):

Definitely +1 on this. It would also be helpful to be able to make certain views shared or even default across users, for a consistent presentation of the information within a team.

@eronlloyd commented on GitHub (Jan 21, 2024): Definitely +1 on this. It would also be helpful to be able to make certain views shared or even default across users, for a consistent presentation of the information within a team.
adam commented 2025-12-29 20:43:58 +01:00
Author
Owner
Copy Link

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

There might be some overlap here with #18458, depending on how we want to handle sharing saved table configurations.

@jeremystretch commented on GitHub (Apr 1, 2025): There might be some overlap here with #18458, depending on how we want to handle sharing saved table configurations.
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 complexity: high netbox 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#8994
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?