Skip to content

[HOLD for payment 2024-08-02] Dupe detect - Billable toggle on confirm page does not reflect the selection on discrepancy page #45864

Closed

Description

@lanitochka17

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: 9.0.10-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

  • Billable feature is enabled on Old Dot.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat
  3. Submit two expenses - Both have the same amount and merchant, but one has enabled billable toggle and the other has disabled billable toggle
  4. Go to transaction thread of the expense that has disabled billable option
  5. Click Review duplicates
  6. Select Keep this one (any)
  7. On "Choose if transaction is billable", select Yes.8. Proceed to confirmation page

Expected Result:

Billable toggle should be enabled as user has chosen Yes on "Choose if transaction is billable" step

Actual Result:

Billable toggle remains disabled on confirmation page when user has chosen Yes on "Choose if transaction is billable" step

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

Bug6548593_1721559579725.bandicam_2024-07-21_18-46-18-580.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @JmillsExpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Jul 21, 2024
  2. melvin-bot commented on Jul 21, 2024

    @melvin-bot

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

  3. github-actions commented on Jul 21, 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.
  4. dominictb commented on Jul 22, 2024

    @dominictb
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    • Billable toggle remains disabled on confirmation page when user has chosen Yes on "Choose if transaction is billable" step

    What is the root cause of that problem?

    What changes do you think we should make in order to solve the problem?

    • Should update it to:
                                isOn={updatedTransaction?.billable ?? !!transactionBillable}
    
  5. mountiny commented on Jul 22, 2024

    @mountiny
    Contributor

    The dupe detection is behind beta so we can demote

    @JmillsExpensify @pecanoro @kubabutkiewicz @parasharrajat

  6. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Jul 22, 2024
  7. parasharrajat commented on Jul 22, 2024

    @parasharrajat
    Member

    @kubabutkiewicz Let's fix this on your PR.

  8. pecanoro commented on Jul 22, 2024

    @pecanoro
    Contributor

    @yuwenmemon I am reassigning the issue to myself so I can review and track the fixes since this is for the duplicate detection project that I am handling.

  9. 13 remaining items

  10. changed the title [-]Dupe detect - Billable toggle on confirm page does not reflect the selection on discrepancy page[/-] [+][HOLD for payment 2024-08-02] Dupe detect - Billable toggle on confirm page does not reflect the selection on discrepancy page[/+] on Jul 26, 2024
  11. melvin-bot commented on Jul 26, 2024

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Jul 26, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.12-0 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-08-02. 🎊

  13. melvin-bot commented on Jul 26, 2024

    @melvin-bot

    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:

    • [@pecanoro] The PR that introduced the bug has been identified. Link to the PR:
    • [@pecanoro] 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:
    • [@pecanoro] 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:
    • [@pecanoro] Determine if we should create a regression test for this bug.
    • [@pecanoro] 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.
    • [@JmillsExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  14. melvin-bot commented on Aug 2, 2024

    @melvin-bot

    Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

  15. melvin-bot commented on Aug 6, 2024

    @melvin-bot

    @JmillsExpensify, @pecanoro Eep! 4 days overdue now. Issues have feelings too...

  16. JmillsExpensify commented on Aug 7, 2024

    @JmillsExpensify
    Contributor

    Payment is being handled in another issue, so going to close this one out.

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

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions