[Due for payment 2025-05-28] [Due for payment 2025-05-27] Expensify Card - Member profile does not include any Expensify Card related information

[jponikarchuk]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.1.46-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/cases/view/3272218
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Windows 10 / Chrome, Samsung Galaxy A12 / Android 13
App Component: Workspace Settings

Action Performed:

Precondition: Have a member of Workspace with Expensify Card assigned.

1. Go to staging.new.expensify.com
2. Go to Workspace
3. Go to Members
4. Click on one of the members

Expected Result:

The member profiles list information related to Expensify Card, such as Assigned cards and a button to assign a new card.

Actual Result:

The member profiles does not list information related to Expensify Card.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

Triggered auto assignment to @mallenexpensify (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]

Triggered auto assignment to @nkuoch (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[nkuoch]

@VickyStash can you look into this? Might be caused by #61706

[VickyStash]

@VickyStash can you look into this? Might be caused by #61706

Yep, taking a look!

[VickyStash]

I've just checked staging, and it works as expected for me:

staging-works.mp4

Do I miss any details?

[joekaufmanexpensify]

Interesting. I just tested on staging and it's not working for me.

2025-05-16_11-22-24.mp4

[VickyStash]

@joekaufmanexpensify Could you please add me as an admin to your workspace? [email protected]

[joekaufmanexpensify]

Done!

[VickyStash]

I'm checking it!

[VickyStash]

I've prepared a PR!
@joekaufmanexpensify @alitoshmatov please take a look

[mvtglobally]

Unable to repro.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.46-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Fix member details display to include any Expensify Card related information #62229

If no regressions arise, payment will be issued on 2025-05-27. 🎊

[melvin-bot]

@nkuoch @mallenexpensify @nkuoch 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]

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.47-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Fix member details display to include any Expensify Card related information #62229

If no regressions arise, payment will be issued on 2025-05-28. 🎊

[melvin-bot]

@nkuoch @mallenexpensify @nkuoch 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]

[alitoshmatov]

I was C+ reviewer in PR, commenting here to be assigned

[mallenexpensify]

Thanks for the ping @alitoshmatov, assigned, I might have missed it.

[alitoshmatov]

BugZero Checklist:

• [Contributor] Classify the bug:

Bug classification

Source of bug:

• 1a. Result of the original design (eg. a case wasn't considered)
• 1b. Mistake during implementation
• 1c. Backend bug
• 1z. Other:

Where bug was reported:

• 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
• 2b. Reported on staging (eg. found during regression or PR testing)
• 2d. Reported on a PR
• 2z. Other:

Who reported the bug:

• 3a. Expensify user
• 3b. Expensify employee
• 3c. Contributor
• 3d. QA
• 3z. Other:

• [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: This was deploy blocker, I think this was mistake during implementation where the case was not considered on this PR - [Internal QA] Update Company Cards logic to show domain cards #61706

• [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: No discussion were created

• [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.

No regression needed, I think there is existing test for this case already.

[mallenexpensify]

Contributor+: @alitoshmatov due $250 via NewDot.

@alitoshmatov think anything needs to be updated for this test?

[alitoshmatov]

@mallenexpensify No, everything looks fine and covers this issue

[melvin-bot]

Payment Summary

Upwork Job

• Reviewer: @alitoshmatov owed $250 via NewDot

BugZero Checklist (@mallenexpensify)

• I have verified the correct assignees and roles are listed above and updated the necessary manual offers
• I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
• I have paid out the Upwork contracts or cancelled the ones that are incorrect
• I have verified the payment summary above is correct