ClearCase indexing misses revisions or indexes revisions multiple times if the server clocks of the ClearCase server and the FishEye servers are out of synch or in different timezones

When FishEye scans ClearCase for changes, it only requests the changes since the last scan date/time. After the scan completes, FishEye records that it has scanned all changes up to the current time. There are a number of issues for which I will create Jiras. The 'lastScannedDateTime' that is recorded is the time on the FishEye server when the scan completed.

• The lastScannedDateTime is not the time that the ClearCase was last queried. So if there are a lot of changes and indexing took some time, any commits performed during indexing will be missed (completely).
• The date/time string that is used does not contain any timezone details, so if the ClearCase server and the FishEye server are in different timezones, bad things will happen.
• The lastScannedDateTime that is recorded is based on the local server time on the FishEye server. If the ClearCase and FishEye servers aren't in synch, some commits will be indexed multiple times or not at all.

The fix is to record the date/time of the last seen change as the lastScannedDateTime. This time is based on the ClearCase servers time.