Skip to content

[Due for payment 2026-02-24] Per Diem - "Fix the distance rate error" is shown when duplicating per diem expense with invalid rate #82275

Closed

Description

@jponikarchuk

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.3.18-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #78792
Email or phone of affected tester (no customers): sjoijsnonisnjidosd@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Workspace has per diem rates.
  1. Open the staging.new.expensify.com website.
  2. Go to workspace chat.
  3. Click + > Create expense > Per diem.
  4. Create a per diem expense.
  5. Go to workspace settings > Per diem.
  6. Select all the rates and delete the rates.
  7. Go back to the per diem expense.
  8. Click More > Duplicate.

Expected Result:

"Fix the per diem rate error" will be shown when duplicating per diem expense with invalid rate.

Actual Result:

"Fix the distance rate error" is shown when duplicating per diem expense with invalid rate.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @kadiealexander

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 12, 2026
  2. melvin-bot commented on Feb 12, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #78792

  3. melvin-bot commented on Feb 12, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  4. melvin-bot commented on Feb 12, 2026

    @melvin-bot

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

  5. github-actions commented on Feb 12, 2026

    @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.
  6. 5 remaining items

  7. JS00001 commented on Feb 12, 2026

    @JS00001
    Contributor

    Demoting, but we'll fix this

  8. added
    ReviewingHas a PR in review
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Feb 12, 2026
  9. changed the title [-]Per Diem - "Fix the distance rate error" is shown when duplicating per diem expense with invalid rate[/-] [+][Due for payment 2026-02-24] Per Diem - "Fix the distance rate error" is shown when duplicating per diem expense with invalid rate[/+] on Feb 17, 2026
  10. melvin-bot commented on Feb 17, 2026

    @melvin-bot

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

  11. melvin-bot commented on Feb 17, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.20-6 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 2026-02-24. 🎊

  12. melvin-bot commented on Feb 17, 2026

    @melvin-bot

    @JS00001 @kadiealexander The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  13. hoangzinh commented on Feb 18, 2026

    @hoangzinh
    Contributor

    I assume we can close this issue and be paid in the original issue.

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.EngineeringWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions