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
[PAID] Tax - Tax rate and tax amount does not update when switching currency offline #42049
Workspace currency default and Foreign currency default are different.
Go to staging.new.expensify.com
Go to workspace chat.
Go offline.
Submit an expense in local currency.
Go to transaction thread.
Click Amount and change it to a foreign currency.
Expected Result:
When changing currency from local to foreign offline, the tax rate and tax amount will update accordingly.
Actual Result:
When changing currency from local to foreign offline, the "Default" label moves to Foreign currency default, but tax rate and tax amount does not update.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open Staging deploy checklist to see the list of PRs included in this release, then work quickly on the following:
If you find which PR caused the issue/bug, you can reassign it to the person responsible for it.
If the author is OOO or won’t get online before the daily deploy is due, you are responsible for finding the best fix/path forward. Don’t hesitate to ask for help!
Try to reproduce the issue, if the bug is on production, remove the DeployBlocker label but stay assigned to fix it (or find out which PR broke it to get help from the author).
You can adjust the urgency of the issue to better represent the gravity of the bug.
If the issue is super low priority, feel free to un-assign yourself.
Be careful with PHP warnings, sometimes it is more complex than just adding a null coalescing operator as they might be uncovering some bigger bug.
If it was a one-off issue that requires no action (for example, Bedrock was down or it is a duplicated issue), you can close it.
Remember rule #2: Never un-assign yourself from a real DeployBlocker unless you are 100% sure someone else is assigned and will take care of it.
👋 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.
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.73-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve 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:
[@rojiphil] The PR that introduced the bug has been identified. Link to the PR:
[@rojiphil] 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:
[@rojiphil] A discussion in #expensify-bugs 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:
[@rojiphil] Determine if we should create a regression test for this bug.
[@rojiphil] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[@strepanier03] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
[@rojiphil] The PR that introduced the bug has been identified. Link to the PR: Offending PR
[@rojiphil] 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: Added comment
[@rojiphil] A discussion in #expensify-bugs 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 Required. Existing checklist good enough to capture such issues.
[@rojiphil] Determine if we should create a regression test for this bug. : A faulty tax rate and amount can result in financial loss to stakeholders. So, it would be better to have a regression test for this.
[@rojiphil] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• Workspace has enabled tax rate.
• Workspace currency default and Foreign currency default are different.
1 Go to workspace chat.
2 Submit an expense in local currency.
3 Go to transaction thread.
4 Click Amount and change it to a foreign currency.
Expected Result: The tax rate should change to that of the default foreign currency and the tax amount should also be updated accordingly.
changed the title [-][HOLD for payment 2024-05-22] Tax - Tax rate and tax amount does not update when switching currency offline[/-][+][PAID] Tax - Tax rate and tax amount does not update when switching currency offline[/+]on May 23, 2024
Activity
melvin-bot commentedon May 13, 2024
Triggered auto assignment to @grgia (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 13, 2024
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open Staging deploy checklist to see the list of PRs included in this release, then work quickly on the following:
Remember rule #2: Never un-assign yourself from a real DeployBlocker unless you are 100% sure someone else is assigned and will take care of it.
melvin-bot commentedon May 13, 2024
Triggered auto assignment to @strepanier03 (
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.github-actions commentedon May 13, 2024
👋 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:
19 remaining items
melvin-bot commentedon May 15, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon May 15, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.73-7 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-05-22. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 15, 2024
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:
strepanier03 commentedon May 21, 2024
@rojiphil - Pay hold comes off tomorrow. I've sent you an offer in Upwork so feel free to finish up the checklist as soon as you're ready.
melvin-bot commentedon May 22, 2024
Payment Summary
Upwork Job
BugZero Checklist (@strepanier03)
rojiphil commentedon May 23, 2024
• Workspace has enabled tax rate.
• Workspace currency default and Foreign currency default are different.
1 Go to workspace chat.
2 Submit an expense in local currency.
3 Go to transaction thread.
4 Click Amount and change it to a foreign currency.
Expected Result: The tax rate should change to that of the
default foreign currencyand the tax amount should also be updated accordingly.rojiphil commentedon May 23, 2024
@strepanier03 Accepted offer and completed checklist here
strepanier03 commentedon May 23, 2024
Thanks @rojiphil - Working on this now.
strepanier03 commentedon May 23, 2024
Created the reg test GH. Paid out and closed the contract in Upwork. Thanks everyone!
[-][HOLD for payment 2024-05-22] Tax - Tax rate and tax amount does not update when switching currency offline[/-][+][PAID] Tax - Tax rate and tax amount does not update when switching currency offline[/+]melvin-bot commentedon Dec 25, 2024
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.