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 2025-10-13] [$250] Workspace - Per diem feature is not enabled on the duplicated workspace #70808
Version Number: 9.2.15-9 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from TestRail:#69146 Email or phone of affected tester (no customers):sdoijdsoisnjdssosd11@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Workspace Settings
Action Performed:
Precondition:
Workspace has imported per diem rates and enabled Per diem feature.
Go to staging.new.expensify.com
Go to Workspaces.
Click 3-dot menu on the workspace.
Click Duplicate workspace.
Click Next > Continue.
Go to the duplicated workspace settings.
Expected Result:
Per diem feature will be enabled on the duplicated workspace.
Actual Result:
Per diem feature is not enabled on the duplicated workspace.
changed the title [-]Workspace - Per diem feature is not enabled on the duplicated workspace[/-][+][$250] Workspace - Per diem feature is not enabled on the duplicated workspace[/+]on Sep 18, 2025
📣 @NagaraniKaleeswaran! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.23-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@hungvu193@joekaufmanexpensify 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]
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Precondition:
Workspace has imported per diem rates and enabled Per diem feature.
Activity
melvin-bot commentedon Sep 18, 2025
Triggered auto assignment to @joekaufmanexpensify (
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.joekaufmanexpensify commentedon Sep 18, 2025
Reproduced.
2025-09-18_10-07-03.mp4
joekaufmanexpensify commentedon Sep 18, 2025
I agree if we copy over per diem rates, we should enable per diem on the workspace by default.
[-]Workspace - Per diem feature is not enabled on the duplicated workspace[/-][+][$250] Workspace - Per diem feature is not enabled on the duplicated workspace[/+]melvin-bot commentedon Sep 18, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021968678614292887758
melvin-bot commentedon Sep 18, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 (
External)NagaraniKaleeswaran commentedon Sep 18, 2025
@MelvinBot
Hi,
Is this task still available to apply?
melvin-bot commentedon Sep 18, 2025
📣 @NagaraniKaleeswaran! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
NagaraniKaleeswaran commentedon Sep 18, 2025
@MelvinBot
Contributor details
Expensify account email: nagaranik2729@gmail.com
Upwork Profile Link: https://www.upwork.com/freelancers/~01513ffa2a648ffb4e?mp_source=share
29 remaining items
melvin-bot commentedon Oct 6, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Oct 6, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.23-3 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 2025-10-13. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Oct 6, 2025
@hungvu193 @joekaufmanexpensify 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]
joekaufmanexpensify commentedon Oct 13, 2025
@hungvu193 could you handle checklist so I can process payment?
melvin-bot commentedon Oct 13, 2025
Payment Summary
Upwork Job
BugZero Checklist (@joekaufmanexpensify)
melvin-bot commentedon Oct 13, 2025
Payment Summary
Upwork Job
BugZero Checklist (@joekaufmanexpensify)
hungvu193 commentedon Oct 14, 2025
BugZero Checklist:
[Contributor] 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: Duplicate workspace #69146
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
joekaufmanexpensify commentedon Oct 14, 2025
Regression issue: https://github.com/Expensify/Expensify/issues/557036
joekaufmanexpensify commentedon Oct 14, 2025
Payment Summary
joekaufmanexpensify commentedon Oct 14, 2025
@hungvu193 please request payment at your earliest convenience. Closing as this is otherwise all set!
JmillsExpensify commentedon Oct 17, 2025
$250 approved for @hungvu193