LCFS - UTC-to-PST conversion

[airinggov]

Description:
Update the transaction history to include timestamps alongside the date for all records. Ensure timestamps are stored in UTC format and displayed on the front end in PST. Adjust the display logic to account for potential changes in day, month, or year based on the UTC-to-PST conversion.

This is already done in Compliance reports so could be replicated from there.

Wireframe:
N/A (Backend-focused change; no major UI modifications beyond updated timestamp display.)

Purpose and benefit to user:
This update provides greater accuracy and clarity for transaction records by including precise timestamps. The conversion from UTC to PST ensures that the displayed date and time are relevant to the user's timezone while maintaining data consistency.

Acceptance Criteria:

• All transaction history records include a timestamp stored in UTC.
• Front-end displays timestamps converted to PST, adjusting the displayed day, month, or year as necessary.
• Testing confirms the accuracy of UTC-to-PST conversions, especially for edge cases around midnight UTC.

Development Checklist:

• Update the database schema to store timestamps in UTC for all transaction history records.
• Implement logic for front-end display of UTC timestamps in PST.
• Validate that the displayed date adjusts correctly based on the UTC-to-PST conversion.
• Add unit and integration tests to ensure:
  • Correct storage of timestamps in UTC.
  • Accurate display of timestamps in PST, including handling of day, month, and year adjustments.
• Review historical transaction records to ensure timestamps are retrofitted accurately without altering original data.

Notes:

• Coordinate with the reporting and analytics teams to verify that downstream systems are compatible with the updated timestamp data.
• Consider potential implications on batch jobs, audits, or time-sensitive reports.
• Provide documentation or user notifications explaining the new timestamp feature and its benefits.