Skip to content

Add View on Spend button to Travel Invoicing settings#97011

Open
ishpaul777 wants to merge 3 commits into
Expensify:mainfrom
ishpaul777:ishpaul/96215-view-on-spend
Open

Add View on Spend button to Travel Invoicing settings#97011
ishpaul777 wants to merge 3 commits into
Expensify:mainfrom
ishpaul777:ishpaul/96215-view-on-spend

Conversation

@ishpaul777

@ishpaul777 ishpaul777 commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Adds a View on Spend button to the Current travel spend row in the Travel Invoicing (Consolidated Travel Billing) settings section. It navigates to the Spend page with a pre-filled query filtered on the Consolidated Travel Billing feed, so admins can drill into and reconcile their travel spend instead of relying on the static PDF statement.

The feed filter uses the Travel Invoicing feed ID ({fundID}_Expensify Card_TRAVEL_US), built via buildQueryStringFromFilterFormValues and routed through ROUTES.SEARCH_ROOT. Per the issue discussion, the query filters on the feed only — no workspace filter.

Fixed Issues

$ #96215
PROPOSAL:

Tests

  1. Sign in as an admin of a workspace with Consolidated Travel Billing enabled.
  2. Go to Workspace settings > More features > Travel.
  3. In the Central invoicing section, find the Current travel spend row.
  4. Verify a grey View on Spend button appears next to the row (and next to the green Pay balance button when a balance is due).
  5. Tap View on Spend.
  6. Verify you land on the Spend page with the query pre-filtered on the Consolidated Travel Billing feed, showing only travel invoicing expenses.
  7. Verify no errors appear in the JS console.
  • Verify that no errors appear in the JS console

Offline tests

  1. Enable Consolidated Travel Billing and open the Travel settings page while online so data is cached.
  2. Turn off the network connection.
  3. Verify the View on Spend button still renders on the Current travel spend row.
  4. Tap View on Spend and verify it navigates to the Spend page (cached results shown; the feed filter is still applied).

QA Steps

  1. Sign in as an admin of a workspace with Consolidated Travel Billing enabled.
  2. Go to Workspace settings > More features > Travel.
  3. In the Central invoicing section, find the Current travel spend row.
  4. Verify the View on Spend button appears next to the row.
  5. Tap View on Spend.
  6. Verify you land on the Spend page pre-filtered on the Consolidated Travel Billing feed.
  • 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 followed proper code patterns (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 followed the guidelines as stated in the Review Guidelines
  • 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 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 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.
  • 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 Screenshot 2026-07-25 at 5 54 40 AM
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop
Screen.Recording.2026-07-25.at.4.17.02.AM.mov

Links admins to the Spend page pre-filtered on the Consolidated Travel
Billing feed so they can reconcile travel spend.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@melvin-bot

melvin-bot Bot commented Jul 24, 2026

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@codecov

codecov Bot commented Jul 24, 2026

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/hooks/useGetExpensifyCardFromReportAction.ts 100.00% <ø> (ø)
src/libs/TravelInvoicingUtils.ts 91.83% <100.00%> (+0.34%) ⬆️
...rkspace/travel/WorkspaceTravelInvoicingSection.tsx 90.90% <80.00%> (-0.71%) ⬇️
... and 8 files with indirect coverage changes

@ishpaul777
ishpaul777 marked this pull request as ready for review July 24, 2026 22:50
@ishpaul777
ishpaul777 requested review from a team as code owners July 24, 2026 22:50
@melvin-bot
melvin-bot Bot requested review from Eskalifer1 and dannymcclain and removed request for a team July 24, 2026 22:50
@melvin-bot

melvin-bot Bot commented Jul 24, 2026

Copy link
Copy Markdown

@dannymcclain @Eskalifer1 One of you needs to 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 flaviadefaria and removed request for a team July 24, 2026 22:50
Comment thread src/pages/workspace/travel/WorkspaceTravelInvoicingSection.tsx
The `{fundID}_{BANK}_{PROGRAM_TRAVEL_US}` feed-ID string was built inline in
WorkspaceTravelInvoicingSection and useGetExpensifyCardFromReportAction. Extract
a getTravelInvoicingFeedID helper in TravelInvoicingUtils and reuse it in both,
so the format lives in one place.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@ishpaul777
ishpaul777 requested a review from blimpich July 24, 2026 23:05

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

Hi, I logged in to my account, where I'm added to the “Test Travel External” workspace, and when I click this button, I should, in theory, only see feed: Consolidated Travel billing, based on this comment:

But for some reason, Expensify Card is also being added—which is expected—yet that specific value isn't shown in the pop-up? Is this a bug?

2026-07-25.14.28.23.mov

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

On a device that's a little over 800px wide, when using a language like Netherlands, the display is very poor—what do you think about that?

2026-07-25.14.35.40.mov

@Eskalifer1

Eskalifer1 commented Jul 25, 2026

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.
  • 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
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants