This is regression with respect to 6.2 (=6.1 Product, where it was working correctly). In that release When user edited which columns were enabled/disabled or resized / moved columns, the table configuration was persisted even after he logged out. When he logged in again, he found the tables how he left them.

In 6.3.0 There seem to be two problems regarding table configuration:
1) When user configures a table, the configuration is no longer persisted after he logs out. When he returns after logout, the tables are again in their initial default state (with regards to which columns are enabled etc.)

2) Another issue (which is more User Experience issue, than bug) is that in tables with multiple filters (like in task list), the individual filters are presented as tabs. The problem I see is, that when user configures the table in one tab, in other tabs the table configuration remains unchanged. Imagine for example that user wants to enable DueOn column in the table - he has to do it for each tab separately. I believe that table configuration for each table with TABS the table configuration should be shared across all the tabs. What do you think?