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
Category visibility - Thread header and thread message does not match #107018
Version Number: 9.5.39-2 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:#105184 Email or phone of affected tester (no customers):joinsdjosjdojosijdiosnj@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.5 / Chrome App Component: Workspace Settings
Action Performed:
Precondition:
Enable categoryVisibility beta.
Create a Control workspace.
Go to staging.new.expensify.com
Go to workspace settings > Members.
Click on your profile.
Click Category visibility.
Unselect any category > Save,
Go to #admins room.
Right click on "set everyone to only see 16 categories" > Reply in thread.
Expected Result:
Thread header and thread message should match.
Actual Result:
Thread header and thread message does not match.
Thread header shows ""set everyone to only see 16 categories".
Thread message shows "vuay al lc.vcnl
Categories: "Car", "Fees", "Home Office", "Insurance", "Interest", "Labor", "Maintenance", "Materials", "Meals and Entertainment", "Office Supplies", "Other", "Professional Services", "Rent", "Taxes", "Travel", and "Utilities".
👋 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.
The thread header requests the compact summary: “set everyone to only see 16 categories.” See computeReportName.ts:517–519.
The parent message inside the thread requests expanded details. For 10 or more categories, the formatter returns the category list instead of the summary sentence. See ReportActionsUtils.ts:3883–3920.
A later review comment expects the compact sentence inside the thread, conflicting with the specification and tests.
The rendering PR reached staging before the reported version. Its web code also reached production, but production feature availability and reproduction remain unverified.
Recommended next action: Confirm whether the thread parent should display expanded details only or the summary plus expanded details. If matching wording is required, prefer a narrow formatter-and-test update over reverting either feature PR.
Confidence: High on the rendering mechanism and introducing PR; whether this constitutes a defect remains unresolved. No browser reproduction or test execution was performed. No code, labels, or assignments were changed.
Demoting, minor UI issue and not blocker worthy. But i agree, threaded headers always show in the body.
So @daledah@nkdengineer, assuming this is the header,
set everyone to only see 16 categories
Can we update the threaded message to be,
set everyone to only see 16 categories
Categories: "Car", "Fees", "Home Office", "Insurance", "Interest", "Labor", "Maintenance", "Materials", "Meals and Entertainment", "Office Supplies", "Other", "Professional Services", "Rent", "Taxes", "Travel", and "Utilities".
Activity
expensify-chore-bot commentedon Nov 16, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #105184
applause-bot commentedon Nov 16, 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/9a2a481d503baf327e4051b606ea222a61372ce3546ad27fe47e4d3e109ea9aa
expensify-chore-bot commentedon Nov 16, 2026
@chiragsalian @daledah you have been assigned to this deploy blocker because you reviewed the offending PR: #105184
expensify-chore-bot commentedon Nov 16, 2026
@nkdengineer you have been assigned to this deploy blocker because you authored the offending PR: #105184
expensify-chore-bot commentedon Nov 16, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 16, 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:
MelvinBot commentedon Nov 16, 2026
Investigation: acceptance criteria conflict
The reported behavior matches the original specification. I recommend clarifying the expected presentation before reverting either PR.
Attribution: Show category visibility change logs in #admins introduced the differing presentations—not the category-visibility picker PR identified by the assignment bot.
Evidence and rendering mechanism
The rendering PR reached staging before the reported version. Its web code also reached production, but production feature availability and reproduction remain unverified.
Recommended next action: Confirm whether the thread parent should display expanded details only or the summary plus expanded details. If matching wording is required, prefer a narrow formatter-and-test update over reverting either feature PR.
Confidence: High on the rendering mechanism and introducing PR; whether this constitutes a defect remains unresolved. No browser reproduction or test execution was performed. No code, labels, or assignments were changed.
view run
chiragsalian commentedon Nov 16, 2026
Demoting, minor UI issue and not blocker worthy. But i agree, threaded headers always show in the body.
So @daledah @nkdengineer, assuming this is the header,
Can we update the threaded message to be,