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
Workspace - Report name works just for a second and changes briefly in online mode #79441
Version Number: v9.3.0-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:#77827 Email or phone of affected tester (no customers):applausetester+piyomn@applause.expensifail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Windows 11 / Chrome App Component: Workspace Settings
Action Performed:
Prerequisites
Create or use an existing Expensifail account (not a personal workspace)
Go to Settings > Workspaces > [Your Workspace] > Reports
Set up a custom default Report Title formula as follow:
{report:type} - {report:total}
Report {report:id} - {report:policyname}
{report:status} Report for {report:workspacename}
Steps:
Open the Expensify app
Click the + button (FAB)
Select Submit Expense
Choose a workspace that has a default custom report title formula
Fill in the expense details (amount, merchant, etc.)
Create the expense
Expected Result:
The expense report should be created with the optimistic report name computed using the formula and remains as "Expense Report - $56.00 Report R00eayCQLmnF - TeamPiyo Open Report for TeamPiyo" without changes to the original report name.
Actual Result:
Report name works just for a second and changes briefly to the original report name
👋 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.
I'm looking into this now. I suspect it only occurs for the beta newExpensifyCustomReportNames. Once I verify that I'll remove the blocker label. That being said, @abbasifaizan70 can we please look into fixing this?
Ok, here's what's going on. In the backend, there is a check for the custom report names beta (isOnAuthAutoReportTitleBeta). It is currently enabled for all accounts by default, based on the global config set on the Concierge account, however the config also specifies that we should excludeDomainStatementReporting. So for any accounts on a domain with a company card that has statement reporting enabled, report names are not computed by the backend for NewDot.
We found that the applause domain has statement reporting enabled, and it was also recently enabled for the expensify.com domain, which is why these users can reproduce the issue. I am not able reproduce the issue on production with an account on the Gmail domain.
Soon we are going to change the beta configuration so that we no longer exclude accounts on domains with statement reporting. In the meantime, applause should be aware that it needs to explicitly enable the beta for the accounts it's testing with SSetNameValuePair('useCustomReportNamesNewExpensify', 'true');, or test with accounts on a different domain.
Activity
melvin-bot commentedon Jan 13, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #77827
melvin-bot commentedon Jan 13, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Jan 13, 2026
Triggered auto assignment to @trjExpensify (
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 Jan 13, 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:
neil-marcellini commentedon Jan 13, 2026
I'm looking into this now. I suspect it only occurs for the beta
newExpensifyCustomReportNames. Once I verify that I'll remove the blocker label. That being said, @abbasifaizan70 can we please look into fixing this?neil-marcellini commentedon Jan 13, 2026
This is not an app deploy blocker, it happens on production too. I suspect a recent Auth change broke something on the backend.
2026-01-13_07-40-25.mp4
neil-marcellini commentedon Jan 13, 2026
Ok, here's what's going on. In the backend, there is a check for the custom report names beta (isOnAuthAutoReportTitleBeta). It is currently enabled for all accounts by default, based on the global config set on the Concierge account, however the config also specifies that we should
excludeDomainStatementReporting. So for any accounts on a domain with a company card that has statement reporting enabled, report names are not computed by the backend for NewDot.We found that the applause domain has statement reporting enabled, and it was also recently enabled for the expensify.com domain, which is why these users can reproduce the issue. I am not able reproduce the issue on production with an account on the Gmail domain.
Soon we are going to change the beta configuration so that we no longer exclude accounts on domains with statement reporting. In the meantime, applause should be aware that it needs to explicitly enable the beta for the accounts it's testing with
SSetNameValuePair('useCustomReportNamesNewExpensify', 'true');, or test with accounts on a different domain.