Skip to content

Show Per Diem Download CSV option before rates are added - #104252

Merged
JS00001 merged 2 commits into
mainfrom
claude-perDiemDownloadCsvBeforeRates
Oct 21, 2026
Merged

JS00001 merged 2 commits into
mainfrom
claude-perDiemDownloadCsvBeforeRates

Conversation

@MelvinBot

@MelvinBot MelvinBot commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

The "Download CSV" option in the Per Diem page's "More" menu was only shown once the workspace had at least one rate. Admins use that download to get the import template with the right headers, so they need it before adding rates (Classic already allows this).

This PR shows "Download CSV" when the workspace has rates or the user can edit Per Diem (canWritePerDiem). Read-only members keep the old behavior, since an empty template isn't useful to someone who can't import.

Fixed Issues

$ #104175
PROPOSAL: #104175 (comment)

Tests

Precondition: Use the staging API (not production).

  1. Go to a workspace > More features > Enable Per diem(Workspace should not have per diem rates - just enabled section)
  2. Go to workspace > Per Diem
  3. Click "More"
  4. Make sure "Download CSV" option is present and works correctly
  • Verify that no errors appear in the JS console

Offline tests

  1. Go to a workspace > More features > Enable Per diem(Workspace should not have per diem rates - just enabled section)
  2. Go to workspace > Per Diem
  3. Click "More"
  4. Make sure "Download CSV" option is present (In offline mode you can't download so "You appear to be offline" modal appears)

QA Steps

Same as tests

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified any copy / text that was added to the app is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

@MelvinBot
MelvinBot requested a review from a team October 16, 2026 15:57
@melvin-bot melvin-bot Bot added Melvin-Test-Android Melvin-Test-Web Triggers Melvin to run the testing steps of the PR on web labels Oct 16, 2026
@MelvinBot

Copy link
Copy Markdown
Contributor Author

I created this PR from an upstream branch because I don't have push access to your fork.

To take ownership of this branch and push updates, run:

git remote add upstream https://github.com/Expensify/App.git
git fetch upstream claude-perDiemDownloadCsvBeforeRates
git checkout -b claude-perDiemDownloadCsvBeforeRates upstream/claude-perDiemDownloadCsvBeforeRates
git push -u origin claude-perDiemDownloadCsvBeforeRates

Then you can close this PR and open a new one from your fork.

@Eskalifer1

Copy link
Copy Markdown
Contributor

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review 🔄 Running since 2026-10-21T10:45:18.568040Z 73ca0ef Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@MelvinBot

Copy link
Copy Markdown
Contributor Author

⚠️ A setup step failed before I could start. This is usually a temporary issue — try again in a few minutes, and if it persists post in #melvinbot-ai.

Run details

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8af1e0fe71

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +240 to 241
if (hasVisibleSubRates || canWritePerDiem) {
menuItems.push({

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Gate the empty-template action on backend support

When an admin has no Per Diem rates, this new condition exposes the download action, but downloadPerDiemCSV() calls ExportPerDiemCSV, which currently rejects that exact case with “No rates found to be exported.” Consequently, the newly enabled action always ends in the download-failed modal and cannot provide the promised import template. This change should be coordinated with the backend support or otherwise generate/provide a valid empty template.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MelvinBot What do you think about that?

Seems like we are wating on BE PR to be deployed: #104175 (comment)

Should we make any action here?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No code change is needed. The Codex finding is valid, but the backend PR already fixes it, so the frontend should not work around it.

I recommend these steps:

  1. Keep this PR in draft, or mark it on hold, until the backend PR deploys. If it merges first, admins on empty workspaces get the "Download failed" modal.
  2. After the backend PR deploys, retest on a workspace with no rates. Clicking "Download CSV" should download a header-only CSV.
  3. Fill in the Tests and QA sections, then mark the PR ready for review.

Building the template in the frontend would duplicate the backend's CSV format and could drift from it, so I don't recommend it.


view run

@MelvinBot

MelvinBot commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor Author

🤖 Web test steps verification results: ✅ pass

On a workspace with Per Diem enabled but no rates, the "More" menu now shows "Download CSV" next to "Import spreadsheet". Clicking it shows the expected "Download failed" modal until the backend fix ships. The PR has no Tests section yet, so I used the reproduction steps from the linked issue.
Download failed modal after clicking Download CSV

Step Status
Go to a workspace you are admin of and open its settingsOpened Settings > Overview for the test user's workspace (user is owner/admin).
Workspace Overview settings page
✅
Enable Per Diem and open the Per Diem page; confirm it shows no ratesPer Diem required upgrading the workspace to Control. After enabling it in More features, the Per Diem page showed the empty state with only an "Import spreadsheet" button and no rates.
More features page with Per diem toggle enabled
Per Diem page empty state, no rates
✅
Click "More"; confirm the menu contains "Download CSV"The menu listed Settings, Import spreadsheet, and Download CSV with zero rates.
More menu open on Per Diem page showing Download CSV option
✅
Click "Download CSV" and record what happensA "Download failed" modal appeared ("Your download couldn't be completed. Please try again later."). This matches the known backend behavior for workspaces with no rates. No console errors.
Download failed modal after clicking Download CSV
✅

view run · view recording

@MelvinBot

Copy link
Copy Markdown
Contributor Author

The failing checks are unrelated to this PR, so I didn't push a fix. main is currently broken, and this PR's CI picks that up when it merges with main.

  • typecheck and test (job 4): Both fail only in tests/actions/IOUTest/SplitTest.ts. This PR changes only src/pages/workspace/perDiem/WorkspacePerDiemPage.tsx. On main, SplitTest.ts passes betas to CreateWorkspaceDataOptions, RequestMoneyInformation, and UpdateSplitTransactionsParams, but those types don't accept betas. These test changes came from Fix report total changing after reverting a split offline, merged today.
  • build (developmentDebug, false): The "Rock Remote Build - Android" step failed and left no error log. A one-file React page change is unlikely to cause this, so it looks flaky. Re-run it.
  • checklist and Check independent approval: These are the normal pending-review checks.

Next step: Once someone fixes SplitTest.ts on main, merge main into this branch or re-run the checks.

Evidence
tests/actions/IOUTest/SplitTest.ts(2710,13): error TS2353: 'betas' does not exist in type 'CreateWorkspaceDataOptions'.
tests/actions/IOUTest/SplitTest.ts(2731,13): error TS2353: 'betas' does not exist in type 'RequestMoneyInformation'.
tests/actions/IOUTest/SplitTest.ts(2808,17): error TS2353: 'betas' does not exist in type 'UpdateSplitTransactionsParams'.

The Jest failures are two updateSplitTransactions rollback tests in the same file, at lines 6762 and 6861.


view run

@MelvinBot

Copy link
Copy Markdown
Contributor Author

I rechecked the checks and still didn't push a fix. The failures come from main, not this PR. This PR changes only src/pages/workspace/perDiem/WorkspacePerDiemPage.tsx.

  • ESLint check (newly failed): src/libs/Navigation/types.ts has 4,001 lines, and the max-lines rule allows 4,000. The file has 4,001 lines on main too, and this PR doesn't touch it.
  • typecheck and test (job 4): These still fail in tests/actions/IOUTest/SplitTest.ts, which passes a betas property that its types don't accept. main still has this code. It came from Fix report total changing after reverting a split offline.
  • Android build: The remote build step failed without an error log. Re-run it.

Next step: After main is fixed, merge main into this branch or re-run the checks.


view run

@MelvinBot

Copy link
Copy Markdown
Contributor Author

I checked again and didn't push a fix. Every failing check still comes from main, not this PR. As of 84dd007, main has not changed in a way that would fix them.

  • typecheck and test (job 4): tests/actions/IOUTest/SplitTest.ts on main still passes a betas property that its types don't accept. This came from Fix report total changing after reverting a split offline.
  • ESLint check: src/libs/Navigation/types.ts on main still has 4,001 lines, one more than max-lines allows.
  • Android build: This failed without an error log. Re-run it.

Merging main now would not help. Ask the author of the SplitTest.ts change to fix main, then merge main into this branch.


view run

@Eskalifer1

Copy link
Copy Markdown
Contributor
Details

Explanation of Change

The "Download CSV" option in the Per Diem page's "More" menu was only shown once the workspace had at least one rate. Admins use that download to get the import template with the right headers, so they need it before adding rates (Classic already allows this).

This PR shows "Download CSV" when the workspace has rates or the user can edit Per Diem (canWritePerDiem). Read-only members keep the old behavior, since an empty template isn't useful to someone who can't import.

Fixed Issues

$ #104175
PROPOSAL: #104175 (comment)

Tests

  1. Go to a workspace > More features > Enable Per diem(Workspace should not have per diem rates - just enabled section)
  2. Go to workspace > Per Diem
  3. Click "More"
  4. Make sure "Download CSV" option is present and works correctly
  • Verify that no errors appear in the JS console

Offline tests

  1. Go to a workspace > More features > Enable Per diem(Workspace should not have per diem rates - just enabled section)
  2. Go to workspace > Per Diem
  3. Click "More"
  4. Make sure "Download CSV" option is present (In offline mode you can't download so "You appear to be offline" modal appears)

QA Steps

Same as tests

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified any copy / text that was added to the app is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

@MelvinBot please set the PR body to the content in the details section above

@MelvinBot

Copy link
Copy Markdown
Contributor Author

I didn't push a fix. Every failing check still comes from main, not this PR. This PR changes only src/pages/workspace/perDiem/WorkspacePerDiemPage.tsx.

  • typecheck and test (job 4): tests/actions/IOUTest/SplitTest.ts on main passes betas to types that no longer accept it.
  • ESLint check: src/libs/Navigation/types.ts on main has 4,001 lines, and the max-lines limit is 4,000.
  • Android build: The remote build step failed with no error log. It looks flaky.
  • checklist and Check independent approval: These wait on the PR checklist and review.

A fix for main is already open: [No QA] Fix max-lines lint, TypeScript and SplitTest failures on main. After it merges, merge main into this branch and the checks should pass. Ask me to do that merge once it lands.


view run

@MelvinBot

Copy link
Copy Markdown
Contributor Author

🤖 Done. I replaced the PR body with the content inside your <details> block. I removed the outer <details> wrapper and kept everything else as you wrote it.

The new body drops the earlier note that the backend currently returns "No rates found to be exported." for workspaces with no rates. Add it back if you want reviewers to expect the "Download failed" modal.


view run

@Eskalifer1

Copy link
Copy Markdown
Contributor

@MelvinBot merge main

@MelvinBot

Copy link
Copy Markdown
Contributor Author

I merged main into this branch. There were no conflicts, and I pushed the merge commit (73ca0ef).


view run

@codecov

codecov Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
...c/pages/workspace/perDiem/WorkspacePerDiemPage.tsx 0.00% <0.00%> (ø)
... and 8 files with indirect coverage changes

@Eskalifer1

Copy link
Copy Markdown
Contributor

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. You're on a roll.

Reviewed commit: 73ca0efe44

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@Eskalifer1

Copy link
Copy Markdown
Contributor

@MelvinBot Let's add precondition to Tests that we should use staging API(not production)

@MelvinBot

Copy link
Copy Markdown
Contributor Author

I added this precondition to the top of the Tests section in the PR description:

Precondition: Use the staging API (not production).

I left Offline tests and QA Steps unchanged. Let me know if you want the precondition there too.


view run

@Eskalifer1

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
104252-android-native.mov
Android: mWeb Chrome
104252-android-web.mov
iOS: HybridApp
104252-ios-native.mov
iOS: mWeb Safari
104252-ios-web.mov
MacOS: Chrome / Safari
104252-web.mov

@Eskalifer1

Copy link
Copy Markdown
Contributor

@codex review

@Eskalifer1

Copy link
Copy Markdown
Contributor

@MelvinBot Mark this PR as ready for review

@MelvinBot
MelvinBot marked this pull request as ready for review October 21, 2026 10:45
@MelvinBot
MelvinBot requested a review from a team as a code owner October 21, 2026 10:45
@melvin-bot
melvin-bot Bot requested a review from Eskalifer1 October 21, 2026 10:45
@MelvinBot

Copy link
Copy Markdown
Contributor Author

I marked this PR as ready for review.


view run

@melvin-bot
melvin-bot Bot removed the request for review from a team October 21, 2026 10:45
@melvin-bot

melvin-bot Bot commented Oct 21, 2026

Copy link
Copy Markdown

@Eskalifer1 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot requested review from heyjennahay and removed request for a team October 21, 2026 10:45
Eskalifer1

This comment was marked as duplicate.

@Eskalifer1 Eskalifer1 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@melvin-bot
melvin-bot Bot requested a review from JS00001 October 21, 2026 10:53
@JS00001
JS00001 merged commit aedd78c into main Oct 21, 2026
50 of 53 checks passed
@JS00001
JS00001 deleted the claude-perDiemDownloadCsvBeforeRates branch October 21, 2026 12:47
@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@github-actions

Copy link
Copy Markdown
Contributor

🚧 JS00001 has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/JS00001 in version: 9.5.16-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@MelvinBot

Copy link
Copy Markdown
Contributor Author

No help site update is needed. This PR only makes Download CSV appear for admins before any rates exist, and no help article says the option requires existing rates.

Details

The closest article is Configure Per Diem in a workspace. It says "Download CSV – Export your current Per Diem rate list." That sentence is still accurate.


view run

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/JS00001 in version: 9.5.18-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 cancelled 🔪

@MelvinBot

Copy link
Copy Markdown
Contributor Author

No help site update needed. This PR only makes Download CSV appear for admins before any Per Diem rates exist, and no sentence in Configure-Per-Diem-in-a-workspace.md says the option is hidden until rates are added, so the article is still accurate.


view run

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/grgia in version: 9.5.18-1 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Melvin-Test-Android Melvin-Test-Web Triggers Melvin to run the testing steps of the PR on web

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants