Skip to content

PM-5839: Render SFDC payment dates consistently - #2138

Merged
jmgasper merged 1 commit into
devfrom
PM-5839
Aug 14, 2026
Merged

PM-5839: Render SFDC payment dates consistently#2138
jmgasper merged 1 commit into
devfrom
PM-5839

Conversation

@jmgasper

Copy link
Copy Markdown
Collaborator

What was broken

Late July 31 SFDC payments could render as August 1 for users whose browser timezone is ahead of America/New_York.

Root cause

The payment table formatted SFDC timestamps in the browser's local timezone even though the report and Salesforce integration use America/New_York calendar dates.

What was changed

Render only SFDC payment-table timestamps explicitly in America/New_York. Billing-account profile dates retain their existing browser-local formatting.

Any added/updated tests

  • Added a Reports page regression using the reported July 31 boundary under Asia/Colombo.
  • Verified the payment remains July 31 while the same instant is August 1 in the browser timezone.
  • Verified billing-account profile dates keep their existing formatting.
  • Focused Reports page tests passed: 2 tests.
  • yarn lint and yarn build passed.
  • The full suite reports 1,081 passing and 27 failing tests. All failures are outside the Reports app; no PM-5839 regression failed.

What was broken

Late July 31 SFDC payments could render as August 1 when the report was viewed from a browser in a positive-offset timezone.

Root cause

The payment table formatted timestamps in the browser's local timezone even though SFDC payment reports use America/New_York calendar dates.

What was changed

Render SFDC payment timestamps explicitly in America/New_York while preserving the existing browser-local formatting for billing-account profile dates.

Any added/updated tests

Added a Reports page regression using the reported July 31 boundary in Asia/Colombo. The test also confirms billing-account profile dates keep their existing formatting.
@jmgasper
jmgasper requested a review from kkartunov as a code owner August 12, 2026 09:55
@jmgasper
jmgasper merged commit d04dbf5 into dev Aug 14, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant