You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-02-24] Per Diem - "Fix the distance rate error" is shown when duplicating per diem expense with invalid rate #82275
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.
Open the staging.new.expensify.com website.
Go to workspace chat.
Click + > Create expense > Per diem.
Create a per diem expense.
Go to workspace settings > Per diem.
Select all the rates and delete the rates.
Go back to the per diem expense.
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
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
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:
@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]
Activity
melvin-bot commentedon Feb 12, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #78792
melvin-bot commentedon Feb 12, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Feb 12, 2026
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.github-actions commentedon Feb 12, 2026
👋 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:
5 remaining items
JS00001 commentedon Feb 12, 2026
Demoting, but we'll fix this
[-]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[/+]melvin-bot commentedon Feb 17, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Feb 17, 2026
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. 🎊
melvin-bot commentedon Feb 17, 2026
@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]
hoangzinh commentedon Feb 18, 2026
I assume we can close this issue and be paid in the original issue.