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
Spend - "Custom Field" columns are not visible if expense is created while in offline mode. #95000
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.
Open the staging.new.expensify.com website.
Navigate to "Workspaces" > Workspace > "Members"
Click on your profile and add any value for "Custom Field 1" and "Custom Field 2"
Navigate to "Spend" > "Expenses"
Click on "Display" > "Edit Columns"
Enable "Custom Field 1" and "Custom Field 2" > "Save"
Turn off internet connection.
Click on FAB and create a manual expense.
Note that after expense is created, "Custom Field 1" and "Custom Field 2" columns are not visible on expense preview.
Turn on internet connection.
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.
👋 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.
Activity
melvin-bot commentedon Jun 30, 2026
@grgia recently merged #90937, but they are OOO right now, so I'll auto-assign someone else.
applause-bot commentedon Jun 30, 2026
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
melvin-bot commentedon Jun 30, 2026
Triggered auto assignment to @blimpich (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jun 30, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jun 30, 2026
👋 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:
blimpich commentedon Jun 30, 2026
I don't consider this a deploy blocker, demoting and assigning as follow up to PR authors
melvin-bot commentedon Jun 30, 2026
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.
grgia commentedon Jul 1, 2026
closing per https://expensify.slack.com/archives/C01GTK53T8Q/p1782838883769929?thread_ts=1782838485.733039&cid=C01GTK53T8Q