[$250] [Due for payment 2025-02-18] Departure time is wrong on trips in trip summary of trip room

[m-natarajan]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.92-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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: @danielrvidal
Slack conversation (hyperlinked to channel name): travel

Action Performed:

1. Book a trip
2. Navigate to trip details
3. Observe the departure time in receipt and trip summary

Expected Result:

Departure time same in both trip summary and receipt

Actual Result:

The departure time is 9:35am PHX time, it shows as 9:02am PHX time in trip summary

Check for screenshots in OP

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Recording.936.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @jliexpensify

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021890162515759570606
• Upwork Job ID: 1890162515759570606
• Last Price Increase: 2025-02-13
• Automatic offers:
• dominictb | Contributor | 106119124

[melvin-bot]

Triggered auto assignment to @jliexpensify (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.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.95-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Fix date formatting #56124

If no regressions arise, payment will be issued on 2025-02-18. 🎊

[melvin-bot]

@stitesExpensify @jliexpensify @stitesExpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[melvin-bot]

@jliexpensify @stitesExpensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[jliexpensify]

@stitesExpensify, it looks like @dominictb was assigned the PR to review. Is this the only payment?

• C+: @dominictb $250

https://www.upwork.com/jobs/~021890162515759570606

[stitesExpensify]

Yes that is correct!

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021890162515759570606

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @getusha (External)

[melvin-bot]

📣 @dominictb 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

[jliexpensify]

Sorry @getusha no memes for you this time