Skip to content

[HOLD for payment 2024-04-05] [$250] [Simplified Collect][Distance rates] No pop-over after bulk-selecting rates and trying to disable/delete them #38876

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.56.0
Reproducible in staging?: y
Reproducible in production?: n
Issue found when executing PR: #38237
Issue reported by: Applause - Internal Team

Action Performed:

precondition: user created a collect policy in OD

  1. Go to https://staging.new.expensify.com/
    and log in as the admin of the collect policy
  2. Navigate to the workspace settings > More features
  3. Enable Distance rates
  4. Open Distance rates
  5. Tap bulk-select
  6. In the drop-down select Disable rates"/ "Delete rates"
  7. On the pop-over tap “Got it”
  8. Delete one distance rate
  9. Tap bulk select > Disable rates/Delete rates

Expected Result:

The same pop-over is displayed in step 6 and 9 notifying that at least one distance rate should be enabled

Actual Result:

The error message "There must be at least one enabled distance rate' is displayed instead of the pop-over the second time trying to disable the distance rates, the error on the distance rate edit screen is shown.

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

Bug6424007_1711171299608.video_2024-03-23_01-21-21.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01da91acddaa976701
  • Upwork Job ID: 1772188427745120256
  • Last Price Increase: 2024-03-25
Issue OwnerCurrent Issue Owner: @sonialiap

Activity

  1. github-actions commented on Mar 23, 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.
  2. kbecciv commented on Mar 23, 2024

    @kbecciv
    Author

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

  3. melvin-bot commented on Mar 23, 2024

    @melvin-bot

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

  4. MrMuzyk commented on Mar 25, 2024

    @MrMuzyk
    Contributor

    I am Michał from Callstack - expert contributor group. I’d like to work on this job.

  5. added
    ExternalAdded to denote the issue can be worked on by a contributor
    and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Mar 25, 2024
  6. 25 remaining items

  7. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Mar 29, 2024
  8. melvin-bot commented on Mar 29, 2024

    @melvin-bot

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

  9. mountiny commented on Mar 29, 2024

    @mountiny
    Contributor

    $250 to @hoangzinh unless you have reviewed the offending PR too?

  10. added and removed on Mar 29, 2024
  11. hoangzinh commented on Mar 30, 2024

    @hoangzinh
    Contributor

    oh nope, the offending PR is not mine. Hehe

  12. sonialiap commented on Apr 5, 2024

    @sonialiap
    Contributor

    @hoangzinh $250 - offer sent

  13. hoangzinh commented on Apr 5, 2024

    @hoangzinh
    Contributor

    Accepted. Thanks @sonialiap

  14. melvin-bot commented on Apr 5, 2024

    @melvin-bot

    Payment Summary

    Upwork Job

    • ROLE: @hoangzinh paid $(AMOUNT) via Upwork (LINK)
    • Contributor: @MrMuzyk is from an agency-contributor and not due payment

    BugZero Checklist (@sonialiap)

    • I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1772188427745120256/hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  15. sonialiap commented on Apr 8, 2024

    @sonialiap
    Contributor

    Payment completed ✔️

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions