Personalized List Columns are reset to column defaults nightly
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2014 08:30 AM
I have an ITIL user who has personalized the list columns in the Release Task List, which shows at the bottom of the Release Form. To personalize she selected "Reset to column defaults" clicked OK and then went back in to update the columns and saved the settings.
Everything stays as she left it for a while, but at some point (at least by overnight) what is displayed seems to reset to the default columns/fields.
The fields that show are the following, which is what the administrator personalized:
Number
Short description
Priority
State
Updated
But when we look at the Selected side she has the following Fields in this order:
Number
Short description
Priority
State
Opened by
Opened
Closed
Assigned to
Any idea what I need to do to allow these personalized list column selections to stick?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2017 09:08 AM
I got an answer from HI. This was a known issue in Geneva (which we are running on Production), and has since been fixed in Helsinki.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2017 07:43 AM
Thanks for the followup Shane.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-07-2017 06:49 AM
This is actually happening again in Instanbul, at least on our Production Instance. So far, just users with the ITIL role, and it seems to be sporadic. I haven't been able to narrow down exactly what our users are doing when it hits them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2018 10:08 AM
We're also seeing this apparent bug on Instanbul. I'm wondering if the issue has persisted to Jakarta?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2018 11:25 AM
From reading some fine print in that problem, it looks like it isn't fixed yet for List V2 (what we are currently using). List V3 has it listed as fixed in Helsinki and after. We have yet to push V3 out to our production, so I can't really verify the problem is no longer occurring.