Skip to content

[Due for payment 2026-01-05] Company card - Card name resets after selecting the same cardholder #78346

Closed

Description

@mitarachim

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


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.
  1. Go to staging.new.expensify.com
  2. Go to workspace settings > Company cards.
  3. Click Assign on any unassigned card.
  4. Select the invited user.
  5. On confirm page, click Card name.
  6. Edit the card name and save it.
  7. Click Cardholder field.
  8. 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.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7035800_1766471663578.17.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @sonialiap

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Dec 23, 2025
  2. melvin-bot commented on Dec 23, 2025

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #78069

  3. melvin-bot commented on Dec 23, 2025

    @melvin-bot

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

  4. melvin-bot commented on Dec 23, 2025

    @melvin-bot

    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.

  5. github-actions commented on Dec 23, 2025

    @github-actions
    Contributor

    👋 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.
  6. hungvu193 commented on Dec 23, 2025

    @hungvu193
  7. hungvu193 commented on Dec 23, 2025

    @hungvu193
    Contributor

    Taking a look

  8. 2 remaining items

  9. MonilBhavsar commented on Dec 23, 2025

    @MonilBhavsar
    Contributor

    Not related to API, so removing DeployBlocker label

  10. m-natarajan commented on Dec 24, 2025

    @m-natarajan

    Issue is not reproducible on Windows 11 / Chrome in v9.2.86-4

    bandicam.2025-12-24.08-19-04-256.mp4
  11. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 26, 2025
  12. 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
  13. melvin-bot commented on Dec 29, 2025

    @melvin-bot

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

  14. melvin-bot commented on Dec 29, 2025

    @melvin-bot

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

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions