This weekend we released an update to FogBugz that affected how we store search indexes. The change went out as part of a group of changes that were intended to improve FogBugz performance. We tested each change individually at a smaller scale and were confident they would improve performance. Under the load of the production environment, however, we saw mail processing and search indexing delays that eventually led to corrupted search indexes for some customers.
Fortunately, FogBugz can automatically rebuild search indexes by resetting the index. We've triggered this rebuild for affected customers.
Rebuilding the index takes time, so it may take a while before all your cases are fully indexed again. During the rebuilding period, you will be notified that search results are incomplete when you perform a search. Note that using search axes like "editedby:me" does not usually rely on the index, so you can still find cases that way. You can also check to see search indexing progress on your Site Configuration page in the Search tab.
Note that this only affects a subset of our customers. If you haven't seen search errors or a notice that your index is being rebuilt, you are totally unaffected by this issue.
