Currently, if a user (in a non-incognito browser) clicks the 'add/remove columns' dropdown on a table and selects columns that are not part of the default visible columns, then that selection will persist for that user even if they exit out of their browser or hard refresh. This could cause an issue for that user if they go back to the report view and see way too many columns, and be puzzled why they'd have to horizontally scroll through the table to see the content. We could remedy this by:
- Adding an auto-expire cookie so that the user column selection reverts back to the default view after 12 hours AND/OR
- Add a table button to revert back to the default view.
This may not be an issue because, presumably, a user that knows how to add a column to the report would also know how to remove a column from the report, and that view would persist for that user until they made another column selection. For this reason, I'm putting this issue in the backlog for now, and we'll address it if we receive user feedback.
Currently, if a user (in a non-incognito browser) clicks the 'add/remove columns' dropdown on a table and selects columns that are not part of the default visible columns, then that selection will persist for that user even if they exit out of their browser or hard refresh. This could cause an issue for that user if they go back to the report view and see way too many columns, and be puzzled why they'd have to horizontally scroll through the table to see the content. We could remedy this by:
This may not be an issue because, presumably, a user that knows how to add a column to the report would also know how to remove a column from the report, and that view would persist for that user until they made another column selection. For this reason, I'm putting this issue in the backlog for now, and we'll address it if we receive user feedback.