<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>With the guidance of Jerry. I was able to verify the fix. 
 
Verified with DataPRO v4.0.1208, 4.2.545, 4.4.232</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2025-04-01T20:12:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-10-17T23:55:31Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-08-24T00:13:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-05-16T21:14:47Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2024-05-07T17:20:34Z</TimeStamp>
    <ReleaseNote>Address a migration issue with test setups from before version 92</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-05-07T17:20:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>50684 is 4.0; 50685 is 4.2; 50686 is 4.3.

To test:
Using the 3.3 db found at
\\dts.local\files\Software\Private\Useful_Test_Files\DataPRO\DB_BACKUPS\MIRA\2023_09_05\3.3\
DataPRO_backup_33_migrated_from_110\DataPRO_backup_33_migrated_from_110.bak, 

install 4.0, 4.2, or 4.3 DataPRO and ensure that there are not multiple entries in the TestSetupROIs table with the same TestSetupId field and blank Suffix fields, which will cause a modal dialog display regarding Multiple ROIs:

(note - not all the test setups in the MIRA database have this issue, so you might want to check multiple or look in the database directly)</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-05-07T16:10:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-05-02T21:04:36Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-05-01T20:59:01Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>The concept of multiple ROIs has evolved so that the RegionsOfInterest column in a TestSetups table in a Version 88 DataPRO database may contain NULL, a string representing one ROI, or a string representing more than one ROI.

When it is NULL, the migration code was creating two entries in the TestSetupROIs table: one (correctly) with the values in the ROIStart and ROIEnd columns, and one (incorrectly) using the -1 for ROIStart and 1 for ROIEnd.</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2024-05-01T20:59:00Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>