Skip to content

Taxes - Tax rate and tax amount take some time to show up in transaction thread #39615

Closed

Description

@kbecciv

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.60-1
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

  • User is an employee of Collect workspace that has taxes.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create a manual request with tax.
  4. Go to transaction thread immediately after the request is created.

Expected Result:

Tax rate and tax amount will instantly show up in transaction thread.

Actual Result:

Tax rate and tax amount take some time to show up in transaction thread.

Workaround:

n/a

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

Bug6437960_1712235526985.bandicam_2024-04-04_20-55-53-264.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~013d484f5c32510e05
  • Upwork Job ID: 1775993187810840576
  • Last Price Increase: 2024-04-04

Activity

  1. melvin-bot commented on Apr 4, 2024

    @melvin-bot

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

  2. github-actions commented on Apr 4, 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.
  3. kbecciv commented on Apr 4, 2024

    @kbecciv
    Author

    We think that this bug might be related to #wave-collect - Release 1

  4. MonilBhavsar commented on Apr 4, 2024

    @MonilBhavsar
    Contributor

    Not a blocker, i think
    We'll be fixing as a regression from #33927

  5. alitoshmatov commented on Apr 4, 2024

    @alitoshmatov
    Contributor

    This is related to offline updates which was not on scope of mentioned PR, and is going to be handled separately, ref: #33927 (comment)

  6. added
    InternalRequires API changes or must be handled by Expensify staff
    BugSomething is broken. Auto assigns a BugZero manager.
    and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Apr 4, 2024
  7. 3 remaining items

  8. melvin-bot commented on Apr 4, 2024

    @melvin-bot

    Triggered auto assignment to Contributor Plus for review of internal employee PR - @mananjadhav (Internal)

  9. melvin-bot commented on Apr 4, 2024

    @melvin-bot

    Triggered auto assignment to @lschurr (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  10. MonilBhavsar commented on Apr 5, 2024

    @MonilBhavsar
    Contributor

    This is related to offline updates which was not on scope of mentioned PR, and is going to be handled separately, ref:

    @alitoshmatov I don't think this is related to offline in any case. This looks an issue with rendering

  11. MonilBhavsar commented on Apr 5, 2024

    @MonilBhavsar
    Contributor
  12. added
    retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause
    on Apr 5, 2024
  13. teneeto commented on Apr 5, 2024

    @teneeto
    Contributor

    Hi, I'm Eto from Callstack - expert contributor group - and I would like to take care of this issue.

  14. MonilBhavsar commented on Apr 8, 2024

    @MonilBhavsar
    Contributor

    Waiting for confirming from QA team (cc @kbecciv)
    If reproducible, Eto Olei will be taking a look

  15. lschurr commented on Apr 8, 2024

    @lschurr
    Contributor
  16. kavimuru commented on Apr 8, 2024

    @kavimuru

    @lschurr issue is fixed now.
    https://github.com/Expensify/App/assets/43996225/32d39438-ccfd-4346-a36e-5b404108d506

    @MonilBhavsar #39804 which was closed as dupe of #39615 still repro. Can we reopen that issue?

  17. MonilBhavsar commented on Apr 9, 2024

    @MonilBhavsar
    Contributor

    Thank you for confirming @kbecciv!
    We can close this issue then


    #39804 is really a duplicate of #39615
    Once #39615 is fixed, #39804 will also be fixed. They have the same root cause - data not being updated optimistically. As a result, there is some delay as data is being returned by server.

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringInternalRequires API changes or must be handled by Expensify staffretest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions