FishEye continually reindexes Base ClearCase changesets made at the same time by different users

Since Base ClearCase does not have a concept of a 'change set', FishEye groups commits made by each user and all the commits made within a second of each other are treated as a change set. FishEye is also storing the number of changes in the database, and upon reindexing, compares the number of items in the changeset to the number previously stored (this is required for the ClearCase UCM support, as UCM activities, which are used as the change sets may be updated after being indexed).

If more than one user has committed changes at the same time, and these changesets have a different number of changes included, then FishEye will continually reindex these changes.