Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Epic: Check in bug tracker and resolution #1838

Open
5 tasks
JackHaeg opened this issue Jan 21, 2025 · 0 comments
Open
5 tasks

Epic: Check in bug tracker and resolution #1838

JackHaeg opened this issue Jan 21, 2025 · 0 comments
Labels
Bug draft Not ready for prioritization yet Epic/Overview Contains a list of other issues or an overview of issue p-feature: Check In Research Researching best approach/solutions role: Back End size: Epic Size not relevant (epic issue)

Comments

@JackHaeg
Copy link
Member

JackHaeg commented Jan 21, 2025

Overview

Associated check in bug issues:

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

Resources/Instructions

@JackHaeg JackHaeg added Bug Epic/Overview Contains a list of other issues or an overview of issue p-feature: Check In role: Back End size: Epic Size not relevant (epic issue) labels Jan 21, 2025
@JackHaeg JackHaeg added this to the 04.01 Existing Features milestone Jan 21, 2025
@github-project-automation github-project-automation bot moved this to New Issue Approval in P: VRMS: Project Board Jan 21, 2025
@JackHaeg JackHaeg moved this from New Issue Approval to Epic Issues in P: VRMS: Project Board Jan 21, 2025
@JackHaeg JackHaeg added Research Researching best approach/solutions draft Not ready for prioritization yet labels Jan 21, 2025
@kurtmgray kurtmgray assigned kurtmgray and unassigned kurtmgray Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug draft Not ready for prioritization yet Epic/Overview Contains a list of other issues or an overview of issue p-feature: Check In Research Researching best approach/solutions role: Back End size: Epic Size not relevant (epic issue)
Projects
Status: Epic Issues
Development

No branches or pull requests

2 participants