Skip to content

Add View transactions shortcut under Current balance#90402

Merged
JS00001 merged 5 commits into
Expensify:mainfrom
neerajbachani:feature/issue-88116-view-transactions-link
Jul 16, 2026
Merged

Add View transactions shortcut under Current balance#90402
JS00001 merged 5 commits into
Expensify:mainfrom
neerajbachani:feature/issue-88116-view-transactions-link

Conversation

@neerajbachani

@neerajbachani neerajbachani commented May 13, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Adds a View transactions TextLink under the Current balance amount on the workspace Expensify Card page. On press, navigates to Search with a canned query using createCardFeedKey(fundID, CONST.EXPENSIFY_CARD.BANK) and ROUTES.SEARCH_ROOT.getRoute({ query }), matching the issue spec (type:expense, feed:…, withdrawn:never, withdrawal-status:pending). The link is shown only when the label type is Current balance (not for remaining limit or cash back). Copy uses existing workspace.common.viewTransactions.

Fixed Issues

$ #88116
PROPOSAL: #88116 (comment)

Tests

  1. Open a workspace where Expensify Card is available; go to WorkspaceExpensify Card.
  2. Confirm Current balance shows a View transactions link under the amount; Remaining limit and Cash back do not show that link.
  3. Tap View transactions and confirm Search opens with a query that includes type:expense, the correct feed:"…" key, withdrawn:never, and withdrawal-status:pending.
  4. Confirm Settle balance / settlement copy (if shown for monthly settlement) still only appears for the Current balance column, not other columns.
  • Verify that no errors appear in the JS console

Offline tests

  1. Same as Tests steps 1–3 while offline (or after toggling offline): View transactions still appears under Current balance only; tapping it queues/opens Search per existing offline navigation behavior.

QA Steps

Same as Tests (workspace Expensify Card page: link placement, navigation to Search, query contents).

  • Verify that no errors appear in the JS console

PR Author Checklist

  • 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 linked the correct issue in the ### Fixed Issues section above
  • 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 any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • 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)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • 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)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • 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.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • 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 IMG_20260518_171423 jpg
Android: mWeb Chrome
lv_0_20260518170928.mp4
iOS: Native Screenshot_2026-05-18-16-46-35-55_99c04817c0de5652397fc8b56c3b3817 jpg
iOS: mWeb Safari
lv_0_20260518163408.online-video-cutter.com.mp4
MacOS: Chrome / Safari
lv_0_20260518163027.mp4

@neerajbachani
neerajbachani requested review from a team as code owners May 13, 2026 03:13
@melvin-bot
melvin-bot Bot requested review from flaviadefaria and mananjadhav and removed request for a team and flaviadefaria May 13, 2026 03:13
@melvin-bot

melvin-bot Bot commented May 13, 2026

Copy link
Copy Markdown

@mananjadhav 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 removed the request for review from a team May 13, 2026 03:13
Comment thread src/pages/workspace/expensifyCard/WorkspaceCardsListLabel.tsx Outdated

const handleViewTransactionsPress = useCallback(() => {
const feedKey = createCardFeedKey(String(defaultFundID), CONST.EXPENSIFY_CARD.BANK);
const query = `type:expense feed:"${feedKey}" withdrawn:never withdrawal-status:pending`;

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.

❌ CONSISTENCY-2 (docs)

The query string contains magic filter keywords (type:expense, withdrawn:never, withdrawal-status:pending) that are not self-explanatory and are not defined as named constants anywhere in the codebase. If these search filter tokens change or need to be reused elsewhere, every occurrence must be found and updated manually.

Extract the search filter components into named constants, for example:

// In CONST or a relevant constants file
const SEARCH_FILTERS = {
    TYPE_EXPENSE: 'type:expense',
    WITHDRAWN_NEVER: 'withdrawn:never',
    WITHDRAWAL_STATUS_PENDING: 'withdrawal-status:pending',
};

// Usage
const query = `${SEARCH_FILTERS.TYPE_EXPENSE} feed:"${feedKey}" ${SEARCH_FILTERS.WITHDRAWN_NEVER} ${SEARCH_FILTERS.WITHDRAWAL_STATUS_PENDING}`;

Reviewed at: 38c6aa3 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@neerajbachani Please address this.

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.

@mananjadhav thanks for the follow up. pulled the type:expense, withdrawn:never, and withdrawal-status:pending fragments into small file-local named constants for readability.

@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: 38c6aa38fe

ℹ️ 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".

};

const handleViewTransactionsPress = useCallback(() => {
const feedKey = createCardFeedKey(String(defaultFundID), CONST.EXPENSIFY_CARD.BANK);

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Preserve missing fund ID when building feed key

useDefaultFundID() falls back to CONST.DEFAULT_NUMBER_ID (0) before a real feed is resolved, but String(defaultFundID) converts that fallback into a truthy value. That makes createCardFeedKey() generate "0_expensify" instead of using its no-fund fallback ("expensify"), so the feed: filter can point to a non-existent feed and return no transactions when users click quickly during initial load (or whenever the fallback is still in effect).

Useful? React with 👍 / 👎.

@codecov

codecov Bot commented May 13, 2026

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
...orkspace/expensifyCard/WorkspaceCardsListLabel.tsx 0.00% <0.00%> (ø)
... and 9 files with indirect coverage changes

@neerajbachani

Copy link
Copy Markdown
Contributor Author

@mananjadhav updated per review: fixed createCardFeedKey (3 args + fund handling for default id), dropped redundant useCallback, and named the search query fragments locally.

@mananjadhav

Copy link
Copy Markdown
Collaborator

@neerajbachani I don't see any screenshots/videos uploaded. Can you please upload them and tag when everything in the checklist is thoroughly verified/completed?

@neerajbachani

Copy link
Copy Markdown
Contributor Author

@mananjadhav Added screenshots/videos for all platforms to the PR description. Please let me know if anything else is needed!

@joekaufmanexpensify
joekaufmanexpensify self-requested a review May 18, 2026 17:54
@github-actions

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@mananjadhav

Copy link
Copy Markdown
Collaborator

Code LGTM, testing it.

@mananjadhav

Copy link
Copy Markdown
Collaborator

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 any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • 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)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • 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)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • 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
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • 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 any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • 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 a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • 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
web-view-transactions.mov

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

The new button looks good to me and it links to what seems to be the correct filters. However, the transactions don't show up. Do we think that's likely an issue with the filters themselves?

image image

@mananjadhav

Copy link
Copy Markdown
Collaborator

@joekaufmanexpensify Can we confirm if Feed: Expensify Card is the correct filter? I don't see any transactions either (that could be because the card added to my workspace).

But when I compare the other filters: type, withdrawal status and withdrawn and check other reports, it seems to be fine. So may be BE is expecting something else for the feed filter?

@mananjadhav mananjadhav left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Approving so that @aldo-expensify can help with the filter check

@melvin-bot
melvin-bot Bot requested a review from aldo-expensify May 19, 2026 16:01
@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

@joekaufmanexpensify Can we confirm if Feed: Expensify Card is the correct filter? I don't see any transactions either (that could be because the card added to my workspace).

It works for me. When I select Feed alone I see transactions. It's just in combination with the other two filters that I don't.

image

@aldo-expensify

Copy link
Copy Markdown
Contributor

@mananjadhav there are some items in your checklist remaining to be check.

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

Issue created. Looking for a volunteer!

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

BE changes are done. We added a new never filter to withdrawal-status. @neerajbachani could we update the shortcut to select both never and pending with withdrawal-status? Those should be the correct filters to use.

@neerajbachani

Copy link
Copy Markdown
Contributor Author

@joekaufmanexpensify Thanks! I'll update the shortcut to use withdrawal-status:never,pending and remove withdrawn:never Waiting on #93895 to merge first since it adds the never value to CONST.SEARCH.SETTLEMENT_STATUS and will push the query update right after

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

Thanks! Bumped that PR just now

@JS00001

JS00001 commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

@neerajbachani the PR above is merged

@mananjadhav

Copy link
Copy Markdown
Collaborator

@neerajbachani Do you now have what is needed to make progress?

@neerajbachani

Copy link
Copy Markdown
Contributor Author

@mananjadhav Yes #93895 is merged and I've pushed the update in commit a907fa4.

The shortcut now uses withdrawal-status:never,pending (removed withdrawn:never) per @joekaufmanexpensify's feedback. Unit test updated and passing locally.

@joekaufmanexpensify Could you re-test on adhoc when you get a chance?

@github-actions

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

Tested on a few accounts and largely working well!

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

I did find one test account where the query seems to be pulling in a bunch of transactions that are between 4-5 years old. When I manually selected only transactions from this year, they exactly match the balance. However, it's unclear to me why there are also these really old Expensify card transactions being listed on the spend page. @JS00001 if I DM you the account, could you assist with taking a look?

image image

@joekaufmanexpensify

Copy link
Copy Markdown
Contributor

Chatted with @JS00001, we might need to clean up one of the backend queries related to these filters. We think there might be a historical issue from when we originally launched the Expensify card in NewDot.

That said, given these filters are already live in the product we don't need to block this app PR on it. It's unlikely this has much impact.

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

Good from my perspective 👍

@JS00001

JS00001 commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

@mananjadhav I think we may need a checklist

@mananjadhav

Copy link
Copy Markdown
Collaborator

Yes. I was waiting on this comment. I'll work on testing this once on my end.

@mananjadhav

Copy link
Copy Markdown
Collaborator

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
web-view-transactions.mov

@mananjadhav mananjadhav left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Still don't have the exact card with transactions, but verify the UI and other parts of the search filter.

And I can see @joekaufmanexpensify checked with a valid card.

@JS00001
JS00001 merged commit fd19be1 into Expensify:main Jul 16, 2026
35 of 38 checks passed
@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.4.36-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

Help site review — changes required ✅

This PR adds a user-facing View transactions link under the Current balance amount on the workspace Expensify Card page (WorkspaceCardsListLabel.tsx), navigating to Search filtered to the transactions that count toward the current balance.

The existing help article that documents the workspace Expensify Card page (Set Up and Manage the Expensify Card) didn't mention this shortcut, so a docs update is warranted.

Draft help site PR: #96357

What the docs PR does
  • Adds a task-based section, How to view the transactions in your Expensify Card current balance, to docs/articles/new-expensify/expensify-card/Set-Up-and-Manage-the-Expensify-Card.md.
  • All UI labels verified against live copy in src/languages/en.ts: Current balance, View transactions, Remaining limit, Cash back.
  • Follows HELPSITE_NAMING_CONVENTIONS.md, HELP_AUTHORING_GUIDELINES.md, and TEMPLATE.md.
  • Labeled HelpDot.

Note: I couldn't set you as the assignee — GitHub rejected the assignment (neerajbachani isn't an assignable collaborator on the repo). Please self-assign the draft PR.

@neerajbachani, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review

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.

7 participants