You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[$250] Status End Time Not Converted to Viewer’s Timezone in NewDot #70797
Version Number: 9.2.15-9 Reproducible in staging?: Y Reproducible in production?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by:@allgandalf Slack conversation (hyperlinked to channel name): #Expensify Bugs
Action Performed:
User A sets a status with an end time in their timezone (e.g., 2:00 PM GST)
User B (in a different timezone, e.g., IST) views User A’s status in DM
Observe the displayed status end time.
Expected Result:
Status end time should be converted and displayed in the viewer’s timezone (e.g., 3:30 PM IST).
Actual Result:
Status end time is shown in the user’s original timezone (e.g., still 2:00 PM).
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
We should add the unit test for getStatusUntilDate to ensure it correctly formats dates according to different time zones and all other cases, such as today, tomorrow, later this year, and dates in another year.
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
Please re-state the problem that we are trying to solve in this issue.
Status end time is not converted to the user time zone.
What is the root cause of that problem?
Currently, we just format and show the date, which is in the user's timezone. For example, if the user's timezone is UTC+8, then inputDate will be in UTC+8.
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
We can test getStatusUntilDate given action actor timezone is different from the current user timezone and verify the date is converted to the current user timezone.
@IuliiaHerets note that you need to be on a different timezone in the other account for eg, the user who sets status should be in dubai timezone and another user who sees it is in IST
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
2b. Reported on staging (eg. found during regression or PR testing)
2d. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: Been a bug since the start. Can't pinpoint a PR
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: Not critical
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon Sep 18, 2025
Triggered auto assignment to @RachCHopkins (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.mukhrr commentedon Sep 18, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
Status End Time Not Converted to Viewer’s Timezone
What is the root cause of that problem?
We use
DateUtils.getStatusUntilDateinReportActionItemSinglefor this tooltip:App/src/pages/home/report/ReportActionItemSingle.tsx
Line 160 in e2e05b5
This is not taking timezone into account:
App/src/libs/DateUtils.ts
Lines 512 to 515 in 9fb00af
What changes do you think we should make in order to solve the problem?
We can pass
originalUserTimezonetogetStatusUntilDatefunction to fix that:And we will take care of timezone like this:
App/src/libs/DateUtils.ts
Lines 520 to 522 in e2e05b5
And we can keep original logic in case we don't provide above timezones.
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
We can add a test case into
ReportActionItemSinglefor that.What alternative solutions did you explore? (Optional)
samranahm commentedon Sep 18, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
Status End Time Not Converted to Viewer’s Timezone in NewDot
What is the root cause of that problem?
We are currently not converting the status clear after to current user's zoned time here
App/src/libs/DateUtils.ts
Lines 515 to 523 in 925b811
What changes do you think we should make in order to solve the problem?
we should use
toZonedTimeto convert the clear after for current user's time zoneApp/src/libs/DateUtils.ts
Lines 515 to 523 in 925b811
and pass the timeZone in both places where we call
getStatusUntilDateApp/src/pages/home/report/ReportActionItemSingle.tsx
Line 160 in 925b811
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
We should add the unit test for
getStatusUntilDateto ensure it correctly formats dates according to different time zones and all other cases, such as today, tomorrow, later this year, and dates in another year.What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
samranahm commentedon Sep 18, 2025
PROPOSAL UPDATED
bernhardoj commentedon Sep 18, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
Status end time is not converted to the user time zone.
What is the root cause of that problem?
Currently, we just format and show the date, which is in the user's timezone. For example, if the user's timezone is UTC+8, then
inputDatewill be in UTC+8.App/src/libs/DateUtils.ts
Lines 512 to 541 in 8e075c2
What changes do you think we should make in order to solve the problem?
First, we need to convert the time to UTC+0 first, and then convert it back to the current user selected timezone.
We can get the
actorTimezonefrom the personal details.App/src/pages/home/report/ReportActionItemSingle.tsx
Line 160 in 8e075c2
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
We can test
getStatusUntilDategiven action actor timezone is different from the current user timezone and verify the date is converted to the current user timezone.RachCHopkins commentedon Sep 22, 2025
I'm not getting this issue on MacOS or Mac Chrome.
Maybe a retest is needed.
IuliiaHerets commentedon Sep 22, 2025
QA team can't repro this issue on Windows 10/Chrome/Build v9.2.16-2
2025-09-22.14-04-22.mp4
allgandalf commentedon Sep 22, 2025
@IuliiaHerets note that you need to be on a different timezone in the other account for eg, the user who sets status should be in dubai timezone and another user who sees it is in IST
samranahm commentedon Sep 22, 2025
@allgandalf, can you send me a message on this Expensify account (samranahmed03@gmail.com) after setting a status end time for 30 minutes later?
RachCHopkins commentedon Sep 23, 2025
@allgandalf can you repro this? I tried with a user account in AEST and mine in NZST and could not repro.
48 remaining items
melvin-bot commentedon Nov 12, 2025
This issue has not been updated in over 15 days. @tgolen, @rushatgabhane, @RachCHopkins, @samranahm eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
samranahm commentedon Nov 13, 2025
@RachCHopkins gentle bump.
RachCHopkins commentedon Nov 16, 2025
Looks like automation is borked. Manually fixing all the things.
RachCHopkins commentedon Nov 16, 2025
Payment Summary:
Upwork job here
RachCHopkins commentedon Nov 16, 2025
@rushatgabhane do we need a regression test?
RachCHopkins commentedon Nov 16, 2025
Contributor has been paid, the contract has been completed, and the Upwork post has been closed.
🟢 to @rushatgabhane to request payment.
rushatgabhane commentedon Nov 24, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: Been a bug since the start. Can't pinpoint a PR
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: Not critical
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/572334
Regression Test Proposal
Test:
Preconditions:
-Have a device in a different timezone, e.g., California [User A]
User A (California) 10:00 AM (PDT)
User B (Netherlands) 7:00 PM (CEST)
Do we agree 👍 or 👎
rushatgabhane commentedon Nov 25, 2025
not overdue
trjExpensify commentedon Dec 5, 2025
approved $250 for @rushatgabhane