Test timestamps in previous daylight savings period generate correct time today

[JackHaeg]

Overview:

It would be helpful for multiple team members to work on this issue individually and show up with results.

A timestamp generated previously before daylight savings hours have changed should generate a timestamp in the current daylight savings time equivalent to the correct hours (e.g., 7pm PST -7 six months ago should generate a timestamp today of 7pm PST -8).

Current overview of Check In Bug per @trillium:

Overview:

• We have accurate timestamps for when the event should start, but the timestamp's date creation is happening sometimes on the day before because of timezone differences between Pacific Time and GMT.
• So, we need to update the backend function to take into account timezone differences of the base timestamp vs. now.

Here's a summary of what happens with events on VRMS:

• A recurring event is generated or updated
  • The front end sends a timestamp with the user's selected time to the backend
  • The backend stores that timestamp in GMT
• Periodically (weekly) the backend runs a script checking to see if any events happen on a day of the week (e.g., Thursday).
  • Within this bucket of events, a new date is generated in today's time and then the hour of that now current timestamp is set to the same hour as the stored recurring event hour.
  • Come check in time, a separate script is run to see if any of the events should be considered open (I believe the window is 30 min before start time and 30 min after the end of the event).
  • If the event's date is off, due to it being created in the wrong timezone (e.g., GMT vs. PST), then when the hour is assigned, the time is roughly off by 1 day or +/- 1 hour.

Action Items:

• Take a look at VRMS/backend/workers/createRecurringEvents.js and write an overview of what this function does.
  • Observe and take note of areas where this code could be refactored into smaller reusable parts.
  • Discuss findings with team.
• Employ agreed upon refactoring suggestions.
  • Include unit tests to ensure functionality.

Resources/Instructions:

• This issue is part of the epic Epic: Check in bug tracker and resolution #1838

[JackHaeg]

Hi @kurtmgray! When you have a moment, can you please provide an update with the following information:

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."

• remember to add links to the top of the issue if they are going to be needed again.