Imported Inspection Schedule Occurs in 1900's

[aj-foster]

Describe the bug

I recently imported an inspection schedule and found the resulting times to be shown as 1926 instead of 2026.

To Reproduce

1. Create an event and add teams.
2. Create an inspection schedule using random assignment.
3. Export the schedule to CSV and manually modify the file as desired. Make no changes to the dates listed (but feel free to change times).
4. Import the modified schedule.
5. See a resulting year as 1926 instead of 2026.

Expected behavior

Expected an inspection schedule using the prescribed date format (YY) to result in 2026 inspection times.

Screenshots

Device (please complete the following information):

• OS: macOS 26
• Browser: Zen/Firefox
• Version: 148

Additional context

This occurred in a dual-division event when importing the schedule to the parent event. It does not appear to affect the team's late status for inspection.

[maths22]

Excel has the unfortunate habit of turning a mm/dd/yyyy date in a csv into a mm/dd/yy date, and the scoring system doesn't handle the second version very well. You can work around the issue by fixing the dates back to full years in a text editor after saving in Excel (or by changing the date format in Excel iirc). (We can look at improving the yy handling, but today we definitely expect yyyy)

[aj-foster]

Oh interesting — I did happen to open the CSV in Excel, and it did do that, but I assume it hadn't because the header says Date (mm/dd/yy).