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 2026-01-05] Company card - Card name resets after selecting the same cardholder #78346
Version Number: 9.2.86-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#78069 Email or phone of affected tester (no customers):applausetester+sdj0mssjsdidnsod1@applause.expensifail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Mac 26.1 / Chrome App Component: Workspace Settings
Action Performed:
Precondition:
User has invited another user to workspace.
Workspace has added a direct feed with card.
Go to staging.new.expensify.com
Go to workspace settings > Company cards.
Click Assign on any unassigned card.
Select the invited user.
On confirm page, click Card name.
Edit the card name and save it.
Click Cardholder field.
Click on the same user.
Expected Result:
Card name will not reset after selecting the same cardholder (similar to production).
Actual Result:
Card name resets after selecting the same cardholder.
👋 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:
Identify the pull request that introduced this issue and revert it.
changed the title [-]Company card - Card name resets after selecting the same cardholder[/-][+][Due for payment 2026-01-05] Company card - Card name resets after selecting the same cardholder[/+]on Dec 29, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.87-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@chiragsalian@sonialiap 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]
Activity
melvin-bot commentedon Dec 23, 2025
You have been assigned to this deploy blocker because you recently merged this PR: #78069
melvin-bot commentedon Dec 23, 2025
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Dec 23, 2025
Triggered auto assignment to @sonialiap (
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.github-actions commentedon Dec 23, 2025
👋 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:
hungvu193 commentedon Dec 23, 2025
hungvu193 commentedon Dec 23, 2025
Taking a look
2 remaining items
MonilBhavsar commentedon Dec 23, 2025
Not related to API, so removing
DeployBlockerlabelm-natarajan commentedon Dec 24, 2025
Issue is not reproducible on Windows 11 / Chrome in v9.2.86-4
bandicam.2025-12-24.08-19-04-256.mp4
[-]Company card - Card name resets after selecting the same cardholder[/-][+][Due for payment 2026-01-05] Company card - Card name resets after selecting the same cardholder[/+]melvin-bot commentedon Dec 29, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.87-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 2026-01-05. 🎊
melvin-bot commentedon Dec 29, 2025
@chiragsalian @sonialiap 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]