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
Distance tax - Tax amount is zero when selecting a distance rate on confirmation page #43111
Issue found when validating #42909 Version Number: 1.4.79-6 Reproducible in staging?: y Reproducible in production?: n 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: Applause internal team Slack conversation:
Action Performed:
Precondition:
Track Tax distance is enabled on Old Dot.
Workspace has a few distance rates and the distance rates are associated with tax rates.
Go to staging.new.expensify.com
Go to workspace chat.
Go to + > Submit expense > Distance.
Enter waypoints > Next.
Click Rate.
Select a distance that has non-zero tax rate.
Expected Result:
The tax amount will update accordingly.
Actual Result:
The tax amount is zero on confirmation page.
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 `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.
@mallenexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
The field Tax reclaimable on should not be 0.00. If you update it to non zero, you should be able to see non zero tax amount. Could you please help to recheck. Thanks!
Activity
melvin-bot commentedon Jun 5, 2024
Triggered auto assignment to @carlosmiceli (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jun 5, 2024
Triggered auto assignment to @mallenexpensify (
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 Jun 5, 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:
m-natarajan commentedon Jun 5, 2024
@mallenexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
m-natarajan commentedon Jun 5, 2024
We think that this bug might be related to #wave-collect - Release 1
MonilBhavsar commentedon Jun 5, 2024
Will look as it is coming from my PR
MonilBhavsar commentedon Jun 5, 2024
Not a Web-E blocker
trjExpensify commentedon Jun 5, 2024
@MonilBhavsar Tax reclaimable portion in the tester's video is $0.00 for all rates:
... so it doesn't matter whatever rate they select. The amount of tax reclaimable on it is
$0.00, so therefore theTax amountis$0.00on the expense:MonilBhavsar commentedon Jun 5, 2024
@m-natarajan this is not a bug and feature -
Here -
The field
Tax reclaimable onshould not be0.00. If you update it to non zero, you should be able to see non zero tax amount. Could you please help to recheck. Thanks!MonilBhavsar commentedon Jun 5, 2024
Lol 😄
trjExpensify commentedon Jun 5, 2024
Hahahahah
carlosmiceli commentedon Jun 5, 2024
Just getting here, not sure I understood if this is a bug or not 😅
trjExpensify commentedon Jun 5, 2024
Not a bug.
carlosmiceli commentedon Jun 5, 2024
Should be closed then, right?
trjExpensify commentedon Jun 5, 2024
Yup!