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
[Due for payment 2025-12-11] Expense - Tax rate is blank after changing expense currency offline #76495
Version Number: 9.2.67-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#74441 Email or phone of affected tester (no customers):jsodijsodijsosjos222w22wsj@gmail.com Issue reported by: Applause Internal Team Device used: Mac 26.1 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Workspace has tax rates.
Workspace currency default tax rate is 5%.
Foreign currency default tax rate is 10%.
Account has self DM.
Go to staging.new.expensify.com
Go to self DM.
Create an expense in workspace default currency.
Open the expense report.
Go offline.
Click Amount, change the currency and save it.
Expected Result:
Tax rate will update to foreign currency default tax rate, which is 10%.
Actual Result:
Tax rate is blank after changing expense currency offline.
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
changed the title [-]Expense - Tax rate is blank after changing expense currency offline[/-][+][Due for payment 2025-12-11] Expense - Tax rate is blank after changing expense currency offline[/+]on Dec 4, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.71-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@robertjchen@johncschuster 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]
Activity
melvin-bot commentedon Dec 2, 2025
Triggered auto assignment to @johncschuster (
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 commentedon Dec 2, 2025
Triggered auto assignment to @robertjchen (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Dec 2, 2025
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
melvin-bot commentedon Dec 2, 2025
💬 A slack conversation has been started in #expensify-open-source
robertjchen commentedon Dec 2, 2025
TBD if it's a blocker here: https://expensify.slack.com/archives/C01GTK53T8Q/p1764660040053729
4 remaining items
melvin-bot commentedon Dec 2, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
[-]Expense - Tax rate is blank after changing expense currency offline[/-][+][Due for payment 2025-12-11] Expense - Tax rate is blank after changing expense currency offline[/+]melvin-bot commentedon Dec 4, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Dec 4, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.71-5 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 2025-12-11. 🎊
melvin-bot commentedon Dec 4, 2025
@robertjchen @johncschuster 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]