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
Insights - "Top Tags" chart is displayed in "Bar" view instead of "Pie" #107216
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):ibellicotest+3215@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome App Component: Other
Action Performed:
Prerequisite: User is owner of a workspace with "Tags" enabled and at least 6 different tags created.
Prerequisite 2: Have more than five tagged expenses created with different tag values.
Open the staging.new.expensify.com website.
Navigate to "Insights"
Scroll down to "Top Tags" chart.
Note that "Top Tags" chart is displayed in "Bar" view instead of being visible as a donut (Pie view)
Expected Result:
"Top Tags" chart should be displayed in "Pie" view (being visible as a donut) with all the used tags ranked.
Actual Result:
Tags are ranked in "Bar" view in "Top Tags" chart instead of being visible in "Pie" view.
👋 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 report does not identify the comparison setting or the number of tag groups remaining after filtering. Having six tags globally does not establish either condition.
Required confirmation: On web, explicitly select Compare → None, with at least two tagged groups inside the selected dates, workspace, and tag level. That should display a donut; Previous period and Average should display bars.
If those expectations pass, this should be treated as expected behavior rather than a blocker. If the no-comparison case still displays bars, retain the blocker and investigate that specific state.
Confidence: High in the intended behavior; unconfirmed explanation for the tester’s session. Investigation was static—no live browser verification was performed. No code or labels changed.
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/3f72684672ad6fb9b98c1639a9181ce6eae8977912060154cdfd863b3ec07414
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
Deploy-blocker investigation
Conclusion: likely expected behavior, not yet a confirmed defect. Do not revert based on the current report.
Add Top tags to the Insights dashboard introduced this feature and is included in the affected staging release. Its specification explicitly calls for:
Code evidence
The report does not identify the comparison setting or the number of tag groups remaining after filtering. Having six tags globally does not establish either condition.
Required confirmation: On web, explicitly select Compare → None, with at least two tagged groups inside the selected dates, workspace, and tag level. That should display a donut; Previous period and Average should display bars.
If those expectations pass, this should be treated as expected behavior rather than a blocker. If the no-comparison case still displays bars, retain the blocker and investigate that specific state.
Confidence: High in the intended behavior; unconfirmed explanation for the tester’s session. Investigation was static—no live browser verification was performed. No code or labels changed.
view run
mhawryluk commentedon Nov 18, 2026
that's expected with
compare:previous-periodluacmartins commentedon Nov 18, 2026
As said above, this is expected. Closing.