Hi, we're having an issue where users are updating, assigning, or transitioning tickets, and when it reindexes or saves or whatnot, it suddenly sets some of our customfields to null. This happens randomly on probably about 1/100 of our issues and we have NO idea why it is.
Here's a screenshot of a changegroup in our database where this happened. The bottom row is the field that the agent wanted to update. The top two rows just got dragged along with it for some reason, and mysteriously got set to null.
Selection_063.png
Another interesting thing is that this seems to happen on the same handful of customfields, several of which are related to our company's revenue--so you see why this is problematic.
My best guess is that this is some kind of bug related to indexing. Just wanted to check if anyone had any ideas or experienced something similar.
Thanks,
Kevin