Skip to content

Tax - Split scan - Selected tax rate is duplicated in Tax rate list #42642

Closed

Description

@m-natarajan

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Issue found when validating #40240
Version Number: 1.4.76-0
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:

  • Workspace is tax enabled.
  • Workspace currency default and Foreign currency default have different tax rate in workspace tax settings.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create a split scan.
  4. When the receipt is scanning, click on the split preview.
  5. Click Amount.
  6. Change the currency to foreign currency.
  7. Enter amount and save it.
  8. Click Tax rate.

Expected Result:

The selected tax rate will not be duplicated.

Actual Result:

The selected tax rate is duplicated.

Workaround:

Unknown

Platforms:

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

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6493019_1716821848213.20240527_225309.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @Christinadobrzyn

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on May 27, 2024
  2. melvin-bot commented on May 27, 2024

    @melvin-bot

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

  3. added
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on May 27, 2024
  4. github-actions commented on May 27, 2024

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  5. melvin-bot commented on May 27, 2024

    @melvin-bot

    Triggered auto assignment to @blimpich (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  6. m-natarajan commented on May 27, 2024

    @m-natarajan
    Author

    @blimpich 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

  7. m-natarajan commented on May 27, 2024

    @m-natarajan
    Author

    We think that this bug might be related to #vip-vsb

  8. blimpich commented on May 27, 2024

    @blimpich
    Contributor

    Looking into this

  9. 19 remaining items

  10. cretadn22 commented on May 29, 2024

    @cretadn22
    Contributor

    @MonilBhavsar Thank you for your recognition of my efforts. After proposing solutions for 4 blockers, it appears they were implemented in the subsequent pull request. Could I suggest raising the bounty to $250 for the effort put into investigating and suggest solutions for those blockers? It seems more fitting than the current $125, which is only half the base price for an issue.

  11. Christinadobrzyn commented on Jun 5, 2024

    @Christinadobrzyn
    Contributor

    checking with @MonilBhavsar on your request @cretadn22

  12. MonilBhavsar commented on Jun 6, 2024

    @MonilBhavsar
    Contributor

    I can't think of a reason why we should not. So I'm fine with paying it. Fine with what others has to say 👍

  13. blimpich commented on Jun 6, 2024

    @blimpich
    Contributor

    Sounds good to me 👍

    @Christinadobrzyn can we pay out $250 to @cretadn22 and then close this issue?

  14. Christinadobrzyn commented on Jun 7, 2024

    @Christinadobrzyn
    Contributor

    Yep! Payouts due:

    Upwork job is here.

    @cretadn22 can you accept? TY!

  15. cretadn22 commented on Jun 7, 2024

    @cretadn22
    Contributor

    @Christinadobrzyn Done 🙏 Thanks so much

  16. cretadn22 commented on Jun 7, 2024

    @cretadn22
    Contributor

    Awaiting payment from @Christinadobrzyn

  17. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    on Jun 7, 2024
  18. Christinadobrzyn commented on Jun 10, 2024

    @Christinadobrzyn
    Contributor

    Thanks @cretadn22 - Paid out based on this payment summary - #42642 (comment)

    Closing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions