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-09-23] [$250] Expensify card - Not here page when open card from another feed #67491
Version Number: v9.1.87-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:**KI retest #65638 Email or phone of affected tester (no customers): - Issue reported by: Applause Internal Team Device used: Windows 11 / Chrome App Component: Other
Action Performed:
Precondition:
User is logged in ND with applause.expensifail.com account.
Workspace A and B are set up with Expensify Card.
Workspace A has at least one other member other than the workspace owner.
STR:
Go to Workspace A settings > Expensify Card.
Open the Expensify Card feed selector.
Select the card feed from Workspace B.
Go to Members > Click on the member.
Click + New card > Go through the process of adding VIRTUAL card and reach confirmation page.
On the confirmation page, click Issue card.
Repeat steps 2-4 with feed from Workspace A
Go to Members > click on member
Click on both cards in Assigned cards
Expected Result:
Card details tab opened for both cards
Actual Result:
Card details tab opened for card from WS A.
Not here page opened for card from WS B
changed the title [-]Expensify card - Not here page when open card from another feed[/-][+][$250] Expensify card - Not here page when open card from another feed[/+]on Aug 7, 2025
Please re-state the problem that we are trying to solve in this issue.
The card details page can’t find a card when opened from different feed.
What is the root cause of that problem?
Cards details was rendered based on last selected WS settings where useDefaultFundID gives it.
And in WorkspaceExpensifyCardDetailsPage.tsxcardsList were coming from last selected WS on Expensify Cards page when you selected from dropdown.
changed the title [-][$250] Expensify card - Not here page when open card from another feed[/-][+][Due for payment 2025-09-23] [$250] Expensify card - Not here page when open card from another feed[/+]on Sep 16, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.14-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@hoangzinh@abekkala 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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon Jul 31, 2025
Triggered auto assignment to @abekkala (
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.melvin-bot commentedon Aug 5, 2025
@abekkala Huh... This is 4 days overdue. Who can take care of this?
[-]Expensify card - Not here page when open card from another feed[/-][+][$250] Expensify card - Not here page when open card from another feed[/+]melvin-bot commentedon Aug 7, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021953484760738718185
melvin-bot commentedon Aug 7, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hoangzinh (
External)mukhrr commentedon Aug 9, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
The card details page can’t find a card when opened from different feed.
What is the root cause of that problem?
Cards details was rendered based on last selected WS settings where
useDefaultFundIDgives it.And in WorkspaceExpensifyCardDetailsPage.tsx
cardsListwere coming from last selected WS on Expensify Cards page when you selected from dropdown.Pay attention to
defaultFundIDhere:What changes do you think we should make in order to solve the problem?
We need to get all WS cards and show by
cardIdon details on L64 in WorkspaceExpensifyCardDetailsPage:What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
cards_<fundID>_Expensify Card: details page finds and renders it.cards_<workspaceAccountID>_Expensify Card: details page finds and renders it.WORKSPACE_CARDS_LISTis loading, page doesn’t incorrectly showNot Found.What alternative solutions did you explore? (Optional)
I thought about passing WS settings to
useDefaultFundIDto prevent it from usinglastSelectedsettings. But i guess this is a bit overhead.hoangzinh commentedon Aug 12, 2025
Thank you for posting proposal, @mukhrr. I will try to review it soon.
27 remaining items
[-][$250] Expensify card - Not here page when open card from another feed[/-][+][Due for payment 2025-09-23] [$250] Expensify card - Not here page when open card from another feed[/+]melvin-bot commentedon Sep 16, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Sep 16, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.14-7 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-09-23. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Sep 16, 2025
@hoangzinh @abekkala 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]
abekkala commentedon Sep 18, 2025
PAYMENT SUMMARY FOR SEPT 23
please complete checklist
hoangzinh commentedon Sep 20, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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: https://github.com/Expensify/App/pull/59887/files#r2365863337
[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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/549709
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
abekkala commentedon Sep 23, 2025
PAYMENT SUMMARY FOR SEPT 23
thanks! 🎉
hoangzinh commentedon Sep 24, 2025
Thanks @abekkala. I requested in ND
garrettmknight commentedon Sep 30, 2025
$250 approved for @hoangzinh