-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2024-06-28] [$250] Timezone in the ND app is not updated after moving to another timezone location #34035
Comments
Triggered auto assignment to @MitchExpensify ( |
Bug0 Triage Checklist (Main S/O)
|
@MitchExpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Not sure how to test this without but going to try with a VPN |
It didn't update after signing out and back in either |
Lastly, I am not sure if this fits into any wave or VIP. What do you think about it being in #vip-vsb @quinthar? |
@MitchExpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@MitchExpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Checking in again on a home for this: https://expensify.slack.com/archives/C066HJM2CAZ/p1705530053332199?thread_ts=1705179873.734529&cid=C066HJM2CAZ |
@MitchExpensify 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! |
It does seem to update after a hard refresh every time for me, would you still consider it a bug if it updates upon refresh @quinthar? |
Friendly bump on the above question @quinthar 👀 |
@MitchExpensify Still overdue 6 days?! Let's take care of this! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.0-9 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-06-28. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Payment summary:
Thoughts on the BZ steps, @alitoshmatov ? |
Regression Test Proposal Prerequisite:
Do we agree 👍 or 👎 |
Not overdue, BZ steps are moving along 👍 |
Ahhh melvin pls 😆 |
As @MitchExpensify is the issue owner, he's the only person who can remove Overdue by commenting. |
@jasperhuangg, @MitchExpensify, @alitoshmatov, @dominictb Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Paid and contract ended for @alitoshmatov I need you to accept this offer to complete your payment @dominictb https://www.upwork.com/nx/wm/offer/102612348 |
@MitchExpensify This issue was created from Jan 5, so as per the announcement the base price (if issue created before April 4) should remain as $500. Could you help to update the offer accordingly? 🙇 🙇 |
I'll issue the additional payment as a bonus if you can accept the existing offer, thanks @dominictb |
@MitchExpensify UW offer accepted, thanks 🚀 |
Nice, paid and contract ended! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.22-0
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: @quinthar
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1704159771205659
Action Performed:
Expected Result:
Timezone is updated in ND to B
Actual Result:
Timezone is not updated
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @MitchExpensifyThe text was updated successfully, but these errors were encountered: