Skip to content

Spend - "Custom Field" columns are not visible if expense is created while in offline mode. #95000

Closed

Description

@applause-bot

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.4.25-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #90937
Email or phone of affected tester (no customers): ibellicotest+2766@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Windows 11 / Chrome
App Component: Search

Action Performed:

Prerequisite: User is owner of a "Control" workspace.
Prerequisite 2: No expenses created yet.

  1. Open the staging.new.expensify.com website.
  2. Navigate to "Workspaces" > Workspace > "Members"
  3. Click on your profile and add any value for "Custom Field 1" and "Custom Field 2"
  4. Navigate to "Spend" > "Expenses"
  5. Click on "Display" > "Edit Columns"
  6. Enable "Custom Field 1" and "Custom Field 2" > "Save"
  7. Turn off internet connection.
  8. Click on FAB and create a manual expense.
  9. Note that after expense is created, "Custom Field 1" and "Custom Field 2" columns are not visible on expense preview.
  10. Turn on internet connection.
  11. Note that now, columns appear correctly.

Expected Result:

"Custom Field 1" and "Custom Field 2" columns should be automatically visible on expenses created while in offline mode.

Actual Result:

"Custom Field 1" and "Custom Field 2" columns are not visible on preview if expense was created while in offline mode.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7195586_1782836035998.Custom_Field.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7195586

Issue OwnerCurrent Issue Owner: @shubham1206agra

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 30, 2026
  2. melvin-bot commented on Jun 30, 2026

    @melvin-bot

    @grgia recently merged #90937, but they are OOO right now, so I'll auto-assign someone else.

  3. applause-bot commented on Jun 30, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/53755d3f597930c5fd0f4fa020e0a6eb15e3afcda3fcca3b657ef29dad915b4e

  4. melvin-bot commented on Jun 30, 2026

    @melvin-bot

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

  5. melvin-bot commented on Jun 30, 2026

    @melvin-bot

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

  6. github-actions commented on Jun 30, 2026

    @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.
  7. blimpich commented on Jun 30, 2026

    @blimpich
    Contributor

    I don't consider this a deploy blocker, demoting and assigning as follow up to PR authors

  8. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Jun 30, 2026
  9. melvin-bot commented on Jun 30, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringHourlyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions