Description
If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.
Version Number: 9.5.41-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: #105096
Email or phone of affected tester (no customers): jiodsnjiojsdio@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Other
Action Performed:
Precondition:
- Enable Tags and add some tags.
- Go to staging.new.expensify.com
- Go to workspace chat.
- Create an expense without category and without tag.
- Go to Insights.
- Scroll down to Top categories and Top tags.
Expected Result:
When there is expense without tag, Top tags should show data with "No tag" bar chart (similar to Top categories).
Actual Result:
When there is expense without tag, Top tags shows Chart unavailable instead of "No tag" bar chart.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome Safari
Screenshots/Videos
Bug7318015_1795017738253.17.mp4
Applause Internal Information
Exported by: Chandana Kiran
Bug ID: 7318015
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsNo status
Activity
applause-bot commentedon Nov 18, 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/6ff95eee99273b53e82b8188c02c9334c83a55ecdba2a5255a8a32f2afaa8766
expensify-chore-bot commentedon Nov 18, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #105096
expensify-chore-bot commentedon Nov 18, 2026
@aldo-expensify @daledah you have been assigned to this deploy blocker because you reviewed the offending PR: #105096
expensify-chore-bot commentedon Nov 18, 2026
@luacmartins you have been assigned to this deploy blocker because you authored the offending PR: #105096
expensify-chore-bot commentedon Nov 18, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 18, 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 18, 2026
🤖 Web test steps verification results: ❌ fail
Web verification was blocked by a blank app and

session_suspendedafter retry; the reported behavior could not be confirmed or disproved. Static investigation identifies the introducing feature, but the exact missing-data mechanism remains unverified.Enable workspace Tags and add tags
Blocked: the browser rendered no interactive content, and the app session remained suspended.Create a workspace expense without category or tag
Not executed because the app was inaccessible.Compare Top tags with Top categories
Runtime comparison was blocked. Static investigation traces the feature to Add Top tags to the Insights dashboard, included in the staging release.Evidence: The PR introduces the Top tags card and level-aware queries. The chart resolver selects the empty state when no positive-count groups exist.
Requirement conflict: The feature PR’s test step 6 explicitly expects an empty state when the selected level has no tagged expenses, whereas this issue expects “No tag.”
Separate defect: The level-aware label branch bypasses missing-tag translation. A label-only fix cannot create a missing aggregate.
Inspect GetInsights response for an untagged group
No response payload was available, so server omission of untagged expenses is not confirmed.Recommendation: Keep the deploy blocker pending confirmation of the intended behavior and capture of the untagged-only response. If the aggregate is missing, labeling changes alone will not resolve this issue. For emergency mitigation, consider a coordinated feature revert; first check overlap with the related Top tags Details-panel changes. A clean standalone revert has not been verified.
view run · no recording available
aldo-expensify commentedon Nov 18, 2026
While showing "No tags" feed a bit more consistent considering this is how the Categories graph behaves, I wouldn't consider this a deploy blocker, and I also think that it may be by design that we are completely excluding expenses without tags from the graph... because otherwise the "No tag" would easily become the "top tag"