change default columns of asset listing tables

[lucasgiovanella]

Hi guys, we are using snipe-it locally in our company, but we would like to customize which columns are displayed as default in the asset listing. Every time we reload the page we have to select the ideal columns for our flow. Thanks.

[snipe]

The column show/hide is stored in local storage. If they’re not being remembered, you likely have something misconfigured. (Also we’d need to know what version you’re using.)

[lucasgiovanella]

Version v7.1.15 - build 16526 (master)

There are no records in the browser that something is being saved, not even in local storage, session storage...

Here is a recording demonstrating the case
https://github.com/user-attachments/assets/c60e5de1-ba6c-420b-94b5-69bbf98f5bb3

[snipe]

Boa tarde @lucasgiovanella,

I never didn't believe you, but that information is either stored in local storage or cookies, so something would either have to be misconfigured or you've got extra security set up on your browser.

Can you reproduce it in the demo? https://demo.snipeitapp.com - if not, it would be something with your local configuration.

[snipe]

(Also that's an older version - might want to upgrade when you can.)

[lucasgiovanella]

version updated. now is Version v8.0.4 - build 17611 (master).
We did some tests and I can explain the problem better. The table that lists all the assets correctly maintains the defined columns when switching between tables, so when leaving the all table and returning to it, the columns remain. However, in the situation tables (installed, in use...), it is different: we define the columns, go to another table, and when we return, the columns are reset, as if they were using an initial state of the table rendering.
The cookies are being set correctly, I apologize for my mistake.

Gravando.2025-04-17.151708.mp4

[snipe]

That's super helpful, thank you! For v8, make sure you also:

• In your .env change BS_TABLE_STORAGE=cookieStorage to BS_TABLE_STORAGE=localStorage.
• Clear your config cache (if you use it): php artisan config:clear

(per #16136, if you haven't done that yet.)

So to clarify, this is only happening on URLs where there's a query string from the sidenav? I can see how that might happen, but I'd like to confirm.

[lucasgiovanella]

Thanks for the tip, problem solved.😁